[SOLVED] Subscription system not updating

U

upnort

Member
Proxmox Subscriber
Apr 26, 2018
111
10
23
The past several weeks we have not been receiving updates on our subscription system. This was a non-subscription system if that matters, but updates had been working fine up until sometime in July.

I reviewed the wiki at https://pve.proxmox.com/wiki/Package_Repositories.

Our /etc/apt/sources.list.d/pve-enterprise.list:

Code: 
deb http://enterprise.proxmox.com/debian/pve stretch pve-enterprise
#deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise

Attempting to use https in the apt sources file results in a Received HTTP code 403 from proxy after CONNECT error.

Code: 
pvesubscription get | egrep '(key|status)'
key: pvexx-xxxxxxxxxx
status: Active

I can log into the repository to browse files with Firefox. I see there are several updates the past few weeks.

No errors reporting when perform apt update and no new updates found.

At this point I don't know if the problem is PEBKAC or the subscription.
 
Thank you Dietmar. We are using apt-cacher-ng. I reconfigured PassThroughPattern and no longer receive an error when using https. One step forward.

Updating results in no updates found. I can see updated packages in the repo when using the web browser portal. Same result if I do not use apt-cacher-ng.
 
upnort said:
Updating results in no updates found. I can see updated packages in the repo when using the web browser portal. Same result if I do not use apt-cacher-ng.
Click to expand...

Most likely something wrong with you apt-cacher-ng setup ...
 
Edit: Refer to the next post. :)

Thank you. At the moment I am not use apt-cacher-ng on the subscription system. :)

This was a non-subscription system before adding the subscription. Running apt results in no updates found.

* Does the subscription repo lag significantly behind the non-subscription repo?

* Could the lack of available updates be a correct reply because of previously using non-subscription packages?

* Our subscription system currently has pve-kernel 4.15.17-3-pve (4.15.17-12) installed. Is this correct?

* Is there a way to revert or reconcile the system with the subscription repository without performing a fresh install?

Thanks again. :)

P.S. The mainline Debian packages are updating. Just the pve packages are not.
 
Last edited:
I found the problem. The clue was moving from a non-subscription system to subscription. I deleted all files in /var/lib/apt/lists. Thereafter apt update succeeded. Yay! :D

I also am again using apt-cacher-ng with https. No problems connecting, although the proxy server does not cache the packages.

As a public service, please consider adding this information in the admin guide/wiki. Then anybody who moves from non-subscription to subscription would be informed to purge the /var/lib/apt/lists non-subscription files. Or perhaps tweak the pvesubscription script (or some other script) to purge the /var/lib/apt/lists non-subscription files when using a subscription. :)
 
upnort said:
I found the problem. The clue was moving from a non-subscription system to subscription. I deleted all files in /var/lib/apt/lists. Thereafter apt update succeeded. Yay! :D

I also am again using apt-cacher-ng with https. No problems connecting, although the proxy server does not cache the packages.

As a public service, please consider adding this information in the admin guide/wiki. Then anybody who moves from non-subscription to subscription would be informed to purge the /var/lib/apt/lists non-subscription files. Or perhaps tweak the pvesubscription script (or some other script) to purge the /var/lib/apt/lists non-subscription files when using a subscription. :)
Click to expand...

you don't need to purge any files. pve-enterprise never contains any packages that were not released via pve-no-subscription beforehand. you simply need to be patient when switching an uptodate pve-no-subscription system to the pve-enterprise repositories - it can take a while until you see new updates available there while they get more exposure in pve-no-subscription.
 
I understand the time lag and package overlap and I expected everything to eventually sync. :-) That did not happen for us. We were weeks out of date with several packages. I knew something was awry because I saw kernel updates across the board with the different distros I maintain. I saw kernel updates for the non-subscription system but saw none for the subscription.

Why purging /var/lib/apt/lists resolved the problem for us I don't know. We've all seen this kind of thing many times in this computer business -- something works for most users but something hiccups for a minority of users. :-)
 
upnort said:
As a public service, please consider adding this information in the admin guide/wiki. Then anybody who moves from non-subscription to subscription would be informed to purge the /var/lib/apt/lists non-subscription files. Or perhaps tweak the pvesubscription script (or some other script) to purge the /var/lib/apt/lists non-subscription files when using a subscription. :)
Click to expand...

Hello,
I have a similar setup (hosts no internetconnection, deb packages via apt-cacher-ng) and ran into the same problems/questions as upnort.
I also think, that it'd be great to expand the documentation for people migrating to the stable repos.

Further on I've got the problem, that after a while the proxmox machines state "invalid: subscription info too old". Giving the hosts Internet access and re-checking the license solves the issue. What are the implications of "invalid: subscription info too old"? Is access to the stable repo still possible? If yes, for how long? Is there a way of avoiding to give the hosts internet access and not running in the "invalid" issue?

Thansk a lot for your help!
 
the online updates do obviously work only if your host able to communicate with our update infrastructure - direct or via proxy.

"invalid: subscription info too old" means, that a previously activated host cannot refresh, as you do not have access to our validation hosts.
 
thanks @tom.
That I understood. But wat are the implications of "invalid: subscription info too old"?
Will the stable repos not talk to my proxmox instances anymore from a certain point on? Or will they serve updates till the license expires regardless of "invalid: subscription info too old"?
 
Xislmo said:
thanks @tom.
That I understood. But wat are the implications of "invalid: subscription info too old"?
..
Click to expand...

This means that there is no subscription active (no online updates via the enterprise update repository).
 
You must log in or register to reply here.
Top Bottom