[SOLVED] No Proxmox pve6to7 in Proxmox 6.4.4

[potetpro]

Hello.

Just setting up a test environment to perform an upgrade from proxmox 6to7 before doing it on our data center.

Not to mention the problems regarding installing the 6.4.4, dunno why this version is so problematic:
https://forum.proxmox.com/threads/installation-problem-no-cdrom-found-and-a-possible-solution.90695/
https://forum.proxmox.com/threads/some-findings-related-to-no-cdrom-found.92108/
Experiencing this version sometimes find the cdrom and sometimes dont. No problem on a new install of proxmox 7.

After getting the installer to work.
And now it stops here:

root@p1:~# apt update && apt upgrade
Hit:1 http://ftp.no.debian.org/debian buster InRelease
Hit:2 http://ftp.no.debian.org/debian buster-updates InRelease
Hit:3 http://security.debian.org buster/updates InRelease
Hit:4 http://download.proxmox.com/debian/ceph-nautilus buster InRelease
Err:5 https://enterprise.proxmox.com/debian/pve buster InRelease
401 Unauthorized [IP: 212.224.123.70 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: 212.224.123.70 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
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.
root@p1:~# pveversion
pve-manager/6.4-4/337d6701 (running kernel: 5.4.106-1-pve)
root@p1:~# pve
pve5to6 pveceph pve-efiboot-tool pve-ha-crm pvemailforward.pl pveproxy pvesm pvesubscription pveupgrade
pveam pvecm pve-firewall pve-ha-lrm pvenode pvereport pvesr pveum pveversion
pvebanner pvedaemon pvefw-logger pvemailforward pveperf pvesh pvestatd pveupdate
root@p1:~# pve6to7
-bash: pve6to7: command not found
root@p1:~#

Proxmox is fully upgraded, and i got pve5to6, but no pve6to7.
This is the latest 6.4 iso downloaded from Proxmox.com

What do?

 

[spirit]

Hello.

Just setting up a test environment to perform an upgrade from proxmox 6to7 before doing it on our data center.

Not to mention the problems regarding installing the 6.4.4, dunno why this version is so problematic:
https://forum.proxmox.com/threads/installation-problem-no-cdrom-found-and-a-possible-solution.90695/
https://forum.proxmox.com/threads/some-findings-related-to-no-cdrom-found.92108/
Experiencing this version sometimes find the cdrom and sometimes dont. No problem on a new install of proxmox 7.

After getting the installer to work.
And now it stops here:

root@p1:~# apt update && apt upgrade
Hit:1 http://ftp.no.debian.org/debian buster InRelease
Hit:2 http://ftp.no.debian.org/debian buster-updates InRelease
Hit:3 http://security.debian.org buster/updates InRelease
Hit:4 http://download.proxmox.com/debian/ceph-nautilus buster InRelease
Err:5 https://enterprise.proxmox.com/debian/pve buster InRelease
401 Unauthorized [IP: 212.224.123.70 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: 212.224.123.70 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
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.
root@p1:~# pveversion
pve-manager/6.4-4/337d6701 (running kernel: 5.4.106-1-pve)
root@p1:~# pve
pve5to6 pveceph pve-efiboot-tool pve-ha-crm pvemailforward.pl pveproxy pvesm pvesubscription pveupgrade
pveam pvecm pve-firewall pve-ha-lrm pvenode pvereport pvesr pveum pveversion
pvebanner pvedaemon pvefw-logger pvemailforward pveperf pvesh pvestatd pveupdate
root@p1:~# pve6to7
-bash: pve6to7: command not found
root@p1:~#

Proxmox is fully upgraded, and i got pve5to6, but no pve6to7.
This is the latest 6.4 iso downloaded from Proxmox.com

What do?

E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 212.224.123.70 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.

you need a subscription license key to use the enterprise repo.

if not, you need to use the non-subscription community repo
https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_no_subscription_repo

 

[potetpro]

Not that error, sorry about that.

The missing pve6to7 binary. And why the pve5to6 is in the Proxmox 6.4.4 release.

Is the pve6to7 only in the enterprise repo?

Edit: We do have licenses on all of our 6 Proxmox servers in our data center.

 

[fiona]

Hi,
you need to upgrade to the latest version of 6.4 first, then you'll have the script available. The upgrade guide mentions this. And as @spirit said, you need to configure a valid repository first, it doesn't have to be the enterprise one.

 

[t.lamprecht]

The missing pve6to7 binary. And why the pve5to6 is in the Proxmox 6.4.4 release.

Because user's would upgrade from 5.4 to 6.4, and the XtoY checker script is useful for ensuring all is OK after the upgrade too, similar to that 6to7 is in 7.x too.

The 6.4 ISO simply did not have the 6to7 tool included yet, as 7.0 only got released months later and such checks cannot be guessed for a future release. Thus, you always need to upgrade to the latest state of your current release first, so that you get all major upgrade preparations, and for that a valid repo is required.

 

[potetpro]

Hi,
you need to upgrade to the latest version of 6.4 first, then you'll have the script available. The upgrade guide mentions this. And as @spirit said, you need to configure a valid repository first, it doesn't have to be the enterprise one.

Thanks, now i see clearly
I have only tested without a subscription 3 years ago, and with subscription the last 3.

Because user's would upgrade from 5.4 to 6.4, and the XtoY checker script is useful for ensuring all is OK after the upgrade too, similar to that 6to7 is in 7.x too.

The 6.4 ISO simply did not have the 6to7 tool included yet, as 7.0 only got released months later and such checks cannot be guessed for a future release. Thus, you always need to upgrade to the latest state of your current release first, so that you get all major upgrade preparations, and for that a valid repo is required.

Yeah, now i see. Thanks for the answer