Hi,
On my 17 nodes cluster I have half of my nodes that won't perform the upgrade from 5.0 to 5.1.
All the missing nodes fails installing pve-cluster, here are the logs:
I did try on one node to reboot and go a little further with no luck by removing then re-installing the list of blocking packages:
pve-cluster pve-firewall libpve-guest-common-perl qemu-server pve-manager libpve-access-control pve-container pve-ha-manager
I've looked around without any luck finding related post.. Did I miss something ?
Regards
On my 17 nodes cluster I have half of my nodes that won't perform the upgrade from 5.0 to 5.1.
All the missing nodes fails installing pve-cluster, here are the logs:
Code:
Paramétrage de wget (1.18-5+deb9u1) ...
Paramétrage de pve-cluster (5.0-15) ...
Job for pve-cluster.service failed because a timeout was exceeded.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
invoke-rc.d: initscript pve-cluster, action "restart" failed.
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Fri 2017-11-03 13:53:56 CET; 7ms ago
Process: 8302 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=killed, signal=TERM)
Process: 8294 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=0/SUCCESS)
Main PID: 8298 (code=killed, signal=KILL)
nov. 03 13:53:42 B1M2 pmxcfs[8298]: [status] notice: members: 2/1606, 3/9075, 4/25076, …48532
nov. 03 13:53:46 B1M2 systemd[1]: pve-cluster.service: Start-post operation timed out. …ping.
nov. 03 13:53:49 B1M2 pmxcfs[8298]: [status] notice: members: 2/1606, 3/9075, 4/25076, …48532
nov. 03 13:53:56 B1M2 systemd[1]: pve-cluster.service: State 'stop-sigterm' timed out. …ling.
nov. 03 13:53:56 B1M2 systemd[1]: pve-cluster.service: Killing process 8298 (pmxcfs) wi…KILL.
nov. 03 13:53:56 B1M2 systemd[1]: pve-cluster.service: Killing process 8302 (pvecm) wit…KILL.
nov. 03 13:53:56 B1M2 systemd[1]: pve-cluster.service: Main process exited, code=killed…/KILL
nov. 03 13:53:56 B1M2 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
nov. 03 13:53:56 B1M2 systemd[1]: pve-cluster.service: Unit entered failed state.
nov. 03 13:53:56 B1M2 systemd[1]: pve-cluster.service: Failed with result 'timeout'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: erreur de traitement du paquet pve-cluster (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Paramétrage de libkrb5-3:amd64 (1.15-1+deb9u1) ...
Paramétrage de dbus (1.10.22-0+deb9u1) ...
A reboot is required to replace the running dbus-daemon.
Please reboot the system when convenient.
Paramétrage de dirmngr (2.1.18-8~deb9u1) ...
dpkg: des problèmes de dépendances empêchent la configuration de pve-firewall :
pve-firewall dépend de pve-cluster ; cependant :
Le paquet pve-cluster n'est pas encore configuré.
dpkg: erreur de traitement du paquet pve-firewall (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de libpve-guest-common-perl :
libpve-guest-common-perl dépend de pve-cluster ; cependant :
Le paquet pve-cluster n'est pas encore configuré.
I did try on one node to reboot and go a little further with no luck by removing then re-installing the list of blocking packages:
pve-cluster pve-firewall libpve-guest-common-perl qemu-server pve-manager libpve-access-control pve-container pve-ha-manager
I've looked around without any luck finding related post.. Did I miss something ?
Regards