Enterprise Repository.

[kleberpaulool]

I have three PMG servers, all with subscription and with the same repositories, including pmg-enterprise.
However, some packages, such as pmg-kernel-6.5, for example, appear available on one of the machines, but do not exist on the others.
How is this possible?

 

[aaron]

That sounds wrong. Have you done a "Refresh" or apt update on all of them recently? Is it possible that the ones on which you do not see the kernel-6.5 as available have it installed already?

Can you post the output of apt update so see if something is going wrong? Ideally inside [CODE][/CODE].

 

[kleberpaulool]

Good afternoon Aaron, thank you for your response.
Yes definitely. apt update, apt upgrade, apt dist-upgrade. All of them.
I also made sure that both /etc/apt/source.lists and /etc/apt/sources.list.d/ are the same on all servers.
Could there be something wrong with my subscriptions?
I can't think of another hypothesis.
If it's the same repository, how can the packages be different?
Can you help me?

 

[aaron]

Can you post the output of apt update so see if something is going wrong? Ideally inside [CODE][/CODE].

 

[kleberpaulool]

root@mx001deb10:~# apt update
Hit:1 http://security.debian.org bookworm-security InRelease
Hit:2 http://ftp.br.debian.org/debian bookworm InRelease                  
Hit:3 http://ftp.br.debian.org/debian bookworm-updates InRelease          
Hit:4 https://enterprise.proxmox.com/debian/pmg bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

 

[kleberpaulool]

apt search proxmox-kernel
Sorting... Done
Full Text Search... Done
proxmox-kernel-6.2/stable,now 6.2.16-19 all [installed,automatic]
  Latest Proxmox Kernel Image

proxmox-kernel-6.2.16-10-pve/stable 6.2.16-10 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-11-pve/stable 6.2.16-11 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-12-pve/stable 6.2.16-12 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-13-pve/stable 6.2.16-13 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-14-pve/stable 6.2.16-14 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-15-pve/stable 6.2.16-15 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-16-pve/stable 6.2.16-16 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-17-pve/stable 6.2.16-17 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-18-pve/stable 6.2.16-18 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-19-pve/stable,now 6.2.16-19 amd64 [installed,automatic]
  Proxmox Kernel Image

proxmox-kernel-6.2.16-6-pve/stable 6.2.16-7 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-8-pve/stable 6.2.16-8 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-9-pve/stable 6.2.16-9 amd64
  Proxmox Kernel Image

proxmox-kernel-helper/stable,now 8.0.3 all [installed,automatic]
  Function for various kernel maintenance tasks.

proxmox-kernel-libc-dev/stable 6.2.16-10 amd64
  Linux support headers for userspace development

.

 

[aaron]

What about the other servers? Is it exactly the same output? Especially the release codename? If they might have been upgraded, one repo might still use bullseye instead of bookworm?

 

[kleberpaulool]

Here's from the other server:

root@mx002deb10:~# apt update
Hit:1 http://ftp.br.debian.org/debian bookworm InRelease
Get:2 http://ftp.br.debian.org/debian bookworm-updates InRelease [52.1 kB]
Hit:3 http://security.debian.org bookworm-security InRelease
Hit:4 https://enterprise.proxmox.com/debian/pmg bookworm InRelease
Fetched 52.1 kB in 1s (40.1 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.


root@mx002deb10:~# apt search proxmox-kernel
Sorting... Done
Full Text Search... Done
proxmox-kernel-6.2/stable 6.2.16-19 all
  Latest Proxmox Kernel Image

proxmox-kernel-6.2.16-10-pve/stable 6.2.16-10 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-11-pve/stable 6.2.16-11 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-12-pve/stable 6.2.16-12 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-13-pve/stable 6.2.16-13 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-14-pve/stable 6.2.16-14 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-15-pve/stable 6.2.16-15 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-16-pve/stable 6.2.16-16 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-17-pve/stable 6.2.16-17 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-18-pve/stable 6.2.16-18 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-19-pve/stable 6.2.16-19 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-6-pve/stable 6.2.16-7 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-8-pve/stable 6.2.16-8 amd64
  Proxmox Kernel Image

proxmox-kernel-6.2.16-9-pve/stable 6.2.16-9 amd64
  Proxmox Kernel Image

proxmox-kernel-6.5/now 6.5.11-7 all [installed,local]
  Latest Proxmox Kernel Image

proxmox-kernel-6.5.11-7-pve-signed/now 6.5.11-7 amd64 [installed,local]
  Proxmox Kernel Image (signed)

proxmox-kernel-helper/now 8.1.0 all [installed,local]
  Function for various kernel maintenance tasks.

proxmox-kernel-libc-dev/stable 6.2.16-10 amd64
  Linux support headers for userspace development

 

[kleberpaulool]

Here's from the other server:
This includes the proxmox-kernel-6.5 and proxmox-kernel-6.5.11-7-pve-signed packages.

 

[aaron]

The kernel 6.5 is not yet available in the Mail Gateway enterprise repository.

proxmox-kernel-6.5/now 6.5.11-7 all [installed,local]

The "local" indicates that these packages were downloaded and installed manually. Maybe from the no-subscription repository? That would explain why the other servers don't have it and don't see it.

 

[kleberpaulool]

I understood.
Is there a way to make all 3 the same?

 

[aaron]

Is it possible that the server with the 6.5 kernel had the no-subscription repository configured before it got a subscription key and the update repo was switched back to the enterprise one?

You could temporarily switch the others to the no-subscription repos and install the newer kernel, but honestly, if they work as expected, there should be no need for it. You could also boot the server with kernel 6.5 with the older 6.2 kernel and remove the 6.5 kernel packages if you want to approach it the other way around

 

[kleberpaulool]

Thank you very much.
This clears up the matter.
Good job.