after upgrade from 5 to 6

S

scorpoin

New Member
Apr 11, 2022
13
0
1
After upgrading promox 5 to 6 . My nodes status turn unknown. I;ve copied the /etc/pve files as well but can not copy them back to /etc/pve permission denied .

pvecm status
Code: 
pvecm status
Cluster information
-------------------
Name:             myCluster
Config Version:   3
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Mon Apr 11 09:24:37 2022
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000003
Ring ID:          3.f
Quorate:          No

Votequorum information
----------------------
Expected votes:   3
Highest expected: 3
Total votes:      1
Quorum:           2 Activity blocked
Flags:          

Membership information
----------------------
    Nodeid      Votes Name
0x00000003          1 192.168.1.12 (local)

all services are running with out error . if there any thing else i should look into .
 
Last edited:
Hi,
sounds like this node is part of a two-node cluster and the other node is down, or at least it cannot communicate with it over the network that's configured for Corosync. Because of that, there is no quorum and so /etc/pve will be read-only. Did you already upgrade the other node too? Did you upgrade to Corosync 3 as mentioned in the upgrade guide?
 
HI,

we had the same issue upgrading proxmox 5 to 6.

The network interfaces have been renamed and bonding interfaces had wrong slaves configured.
 
Fabian_E said:
Hi,
sounds like this node is part of a two-node cluster and the other node is down, or at least it cannot communicate with it over the network that's configured for Corosync. Because of that, there is no quorum and so /etc/pve will be read-only. Did you already upgrade the other node too? Did you upgrade to Corosync 3 as mentioned in the upgrade guide?
Click to expand...
I have followed same guide , on update getting following errors

Code: 
Err:5 https://enterprise.proxmox.com/debian/pve buster Release
  401  Unauthorized
Err:2 http://download.proxmox.com/debian/pve buster InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7BF2812E8A6E88E0
Err:3 http://security.debian.org/debian-security buster/updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853
Get:6 http://debian.mirrors.ovh.net/debian buster InRelease [122 kB]
Get:7 http://debian.mirrors.ovh.net/debian buster-updates InRelease [51.9 kB]   
Err:6 http://debian.mirrors.ovh.net/debian buster InRelease                     
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY DCC9EFBF77E11517
Err:7 http://debian.mirrors.ovh.net/debian buster-updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9
Reading package lists... Done
E: The repository 'https://enterprise.proxmox.com/debian/pve buster Release' does not 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.
W: GPG error: http://download.proxmox.com/debian/pve buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7BF2812E8A6E88E0
E: The repository 'http://download.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.
W: GPG error: http://security.debian.org/debian-security buster/updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853
E: The repository 'http://security.debian.org/debian-security buster/updates 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.
W: GPG error: http://debian.mirrors.ovh.net/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY DCC9EFBF77E11517
E: The repository 'http://debian.mirrors.ovh.net/debian 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.
W: GPG error: http://debian.mirrors.ovh.net/debian buster-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9
E: The repository 'http://debian.mirrors.ovh.net/debian buster-updates 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.

Any thing I did wrong? I added repository just and run apt update , but failed with above errors.
 
scorpoin said:
I have followed same guide , on update getting following errors

Code: 
Err:5 https://enterprise.proxmox.com/debian/pve buster Release
  401  Unauthorized
Click to expand...
To access the enterprise repository, you need a valid subscription. If you don't have one, disable the repository and configure the pve-no-subscription repository instead (see here)

scorpoin said:
Err:2 http://download.proxmox.com/debian/pve buster InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7BF2812E8A6E88E0
Err:3 http://security.debian.org/debian-security buster/updates InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853
Get:6 http://debian.mirrors.ovh.net/debian buster InRelease [122 kB]
Get:7 http://debian.mirrors.ovh.net/debian buster-updates InRelease [51.9 kB]
Err:6 http://debian.mirrors.ovh.net/debian buster InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY DCC9EFBF77E11517
Err:7 http://debian.mirrors.ovh.net/debian buster-updates InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9
Reading package lists... Done
E: The repository 'https://enterprise.proxmox.com/debian/pve buster Release' does not 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.
W: GPG error: http://download.proxmox.com/debian/pve buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7BF2812E8A6E88E0
E: The repository 'http://download.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.
W: GPG error: http://security.debian.org/debian-security buster/updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853
E: The repository 'http://security.debian.org/debian-security buster/updates 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.
W: GPG error: http://debian.mirrors.ovh.net/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY DCC9EFBF77E11517
E: The repository 'http://debian.mirrors.ovh.net/debian 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.
W: GPG error: http://debian.mirrors.ovh.net/debian buster-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9
E: The repository 'http://debian.mirrors.ovh.net/debian buster-updates 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.
[/CODE]
Click to expand...
Seems like there is a problem with the trusted keys. What does ls /etc/apt/trusted.gpg.d show? What is the output of pveversion -v?

scorpoin said:
Any thing I did wrong? I added repository just and run apt update , but failed with above errors.
Click to expand...
Which repository did you add?
 
Fabian_E said:
To access the enterprise repository, you need a valid subscription. If you don't have one, disable the repository and configure the pve-no-subscription repository instead (see here)


Seems like there is a problem with the trusted keys. What does ls /etc/apt/trusted.gpg.d show? What is the output of pveversion -v?


Which repository did you add?
Click to expand...
pveversion -v
Code: 
ve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.17-1-pve: 4.10.17-16
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.5-1~bpo9+2
pve-cluster: 5.0-12
qemu-server: 5.0-14
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: not correctly installed
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

ls /etc/apt/trusted.gpg.d
Code: 
debian-archive-jessie-automatic.gpg           debian-archive-stretch-automatic.gpg           debian-archive-wheezy-automatic.gpg
debian-archive-jessie-security-automatic.gpg  debian-archive-stretch-security-automatic.gpg  debian-archive-wheezy-stable.gpg
debian-archive-jessie-stable.gpg              debian-archive-stretch-stable.gpg              proxmox-ve-release-5.x.gpg
 
You need to upgrade to the latest version of 5.x before upgrading to 6.x. So I'd switch the repositories back to stretch and do that first. And you should upgrade to Corosync 3 while still on stretch as the upgrade guide mentions.
 
I've added coronsyn repository and run apt update and then upgrade everything works fine and upgrade from 5.x to 6.x . Nodes were up and running. I just stop one vm to make a backup of it. Now getting this error

Code: 
Connection error 401: 403 Permission check failed (permission denied - invalid PVE ticket)

how do I fix this issue.
 
Where exactly does the error show up? Is there anything relevant in /var/log/syslog or /var/log/pveproxy/access.log?
 
You must log in or register to reply here.
Top Bottom