node cluster hard reboot now dropped

[yaboc]

hi

mistakenly i did a hard reset to a node #2 in a 4 node cluster and now the node is gone from the cluster when i try to readd it says

authentication key already exists

is there a way to readd it? are the VMs going to start up ?

im on 4.2-2/725d76f0

Thanks

 

[yaboc]

i tried to force the node add back to the cluster and now it appears on the master node but restarting the cluster service on the added node fails with

Restarting pve-cluster (via systemctl): pve-cluster.serviceJob for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
failed!

 

[yaboc]

i'd like to resintall pve on this node but it's failing

@px2:~# apt-get install proxmox-ve
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
proxmox-ve
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
5 not fully installed or removed.
Need to get 4,726 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://download.proxmox.com/debian/ jessie/pve-no-subscription proxmox-ve all 4.2-49 [4,726 B]
Fetched 4,726 B in 0s (14.3 kB/s)
Selecting previously unselected package proxmox-ve.
(Reading database ... 55356 files and directories currently installed.)
Preparing to unpack .../proxmox-ve_4.2-49_all.deb ...
Unpacking proxmox-ve (4.2-49) ...
Setting up pve-firewall (2.0-26) ...
Failed to reload-or-restart pve-firewall.service: Unit pve-firewall.service is masked.
dpkg: error processing package pve-firewall (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured

 

[Mr.Embedded]

You need to unmask it. Check its status by:

systemctl list-unit-files

Its probably masked so unmask it:

systemctl unmask pve-firewall.service

 

[Coneng]

Thank you that helped with migrating to version 5

 

[manu]

for the record, we fixed this issue in pve-firewall 3.0-2 ( available for the moment in pvetest)