TASK ERROR: command 'apt-get update' failed: exit code 100

[marcosch]

Hi all,

Since the first of October I've the following error at PROXMOX:

TASK ERROR: command 'apt-get update' failed: exit code 100


If I do the "apt-get update" manually on the system, I get the following:

schm@charles:~$ sudo apt-get update
[sudo] password for schm:
Ign:1 http://ftp.ch.debian.org/debian stretch InRelease
Hit:2 http://security.debian.org stretch/updates InRelease
Hit:3 http://ftp.ch.debian.org/debian stretch-updates InRelease
Hit:4 http://ftp.ch.debian.org/debian stretch Release
Ign:6 https://enterprise.proxmox.com/debian/pve stretch InRelease
Err:7 https://enterprise.proxmox.com/debian/pve stretch Release
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Reading package lists... Done
E: The repository 'https://enterprise.proxmox.com/debian/pve stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


Why do I've this error, what has changed on 01.10.2021?
Do you know what I've to do to fix this?

Many thanks & best regards,
Marco

 

[fabian]

stretch / pve 5 is no longer supported (they are end of life for over a year already). you are probably bitten by the (old) Let's Encrypt root certificate expiring:

https://community.letsencrypt.org/t...changes-for-let-s-encrypt-certificates/143816
https://community.letsencrypt.org/t/production-chain-changes/150739

 

[marcosch]

stretch / pve 5 is no longer supported (they are end of life for over a year already). you are probably bitten by the (old) Let's Encrypt root certificate expiring:

https://community.letsencrypt.org/t...changes-for-let-s-encrypt-certificates/143816
https://community.letsencrypt.org/t/production-chain-changes/150739

Many thanks for your feedback.

1. So you mean, if I upgrade from my Proxmox 5.4-13 to the latest&greatest, I don't have this error anymore?

2. I need to upgrade, because you said it's end-of-life for over a year! But why we get still "communitiy licenses" for this old proxmox version?

3. Can I upgrade directly from 5.4.13 to 7? Will my VMs runs without any problems on this new Proxmox 7?


I really need help, I'm not a specialist in Proxmox ;-)

 

[fabian]

Many thanks for your feedback.

1. So you mean, if I upgrade from my Proxmox 5.4-13 to the latest&greatest, I don't have this error anymore?

2. I need to upgrade, because you said it's end-of-life for over a year! But why we get still "communitiy licenses" for this old proxmox version?

3. Can I upgrade directly from 5.4.13 to 7? Will my VMs runs without any problems on this new Proxmox 7?


I really need help, I'm not a specialist in Proxmox ;-)

1. you should update in any case
2. because the subscriptions are not version specific (EOL releases are not covered by support though!)
3. no, you need to upgrade to latest 5.x first, then latest 6.x, then latest 7.x

 

[marcosch]

1. you should update in any case
2. because the subscriptions are not version specific (EOL releases are not covered by support though!)
3. no, you need to upgrade to latest 5.x first, then latest 6.x, then latest 7.x

Many thanks for your feedback.

Okay, that means I will plan the upgrade for this month:

Regarding the second point: If I've problems during the upgrade, I won't get support?

Regarding the third point:
- I'm on 5.4-13, so it means I'm on the latest 5.x, right?
- For the upgrade 5 to 6 I will use the following URL: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
- For the upgrade 6 to 7 I will use the following URL: https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

Do you have in general some tips/hints for my comming upgrade?

 

[fabian]

we won't leave you standing in the rain (and the upgrade SHOULD work the same as it did back when it was still actively supported), but it's not covered by our enterprise support agreement anymore.

if you have a cluster, pay special attention to the instructions regarding that (especially from 5 to 6). same goes for Ceph.

 

[marcosch]

we won't leave you standing in the rain (and the upgrade SHOULD work the same as it did back when it was still actively supported), but it's not covered by our enterprise support agreement anymore.

if you have a cluster, pay special attention to the instructions regarding that (especially from 5 to 6). same goes for Ceph.

Okay, but one thing I don't understand:

In the above documentation (5 to 6) I can read the following:

First, make sure that the system is running using the latest Proxmox VE 5.4 packages:
apt update
apt dist-upgrade

... but this won't work because of my certificate issue!?

 

[fabian]

you can temporarily switch to the no-subscription repo for 5.x - it is identical content-wise to the enterprise one since neither receives any more updates.

 

[marcosch]

you can temporarily switch to the no-subscription repo for 5.x - it is identical content-wise to the enterprise one since neither receives any more updates.

so you mean I've to add to the following file:

/etc/apt/sources.list

... this repo:

deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

Is this the right way to go?
And what I have to do with /etc/apt/sources.list.d/pve-enterprise.list, delete it?

 

[fabian]

yes. after the upgrade to buster, re-enable the enterprise repo and remove the no-subscription one.

 

[marcosch]

Hi all

Does Proxmox 7 runs old Linux virtual machines, like CentOS 6/7 and Debian 5?

Many thanks for your feedback.

Best regards,
Marco

 

[fabian]

as VMs, yes (might require some special care when configuring if the kernel is really really old, and some features like cpu/memory hotplug might not work). as containers, many legacy/EOL distros don't work anymore in a modern container environment.