Proxmox VE 4.0 released!

informant said:
Hi, we have following error on apt-get update:

Code: 
W: Fehlschlag beim Holen von http://download.proxmox.com/debian/dists/jessie/Release  Erwarteter Eintrag »pve/binary-amd64/Packages« konnte in Release-Datei nicht gefunden werden (falscher Eintrag in sources.list oder missgebildete Datei).

What can we do here? I mean, you have no pve entry in your source-list on http://download.proxmox.com/debian/dists/jessie/Release only pvetest and no-subscription...

sourcelist.conf:
Code: 
deb http://ftp.de.debian.org/debian jessie main contrib non-free
deb-src http://ftp.de.debian.org/debian jessie main contrib non-free

deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free

# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian jessie pve

# PVE pve-no-subscription repository provided by proxmox.com, NOT recommended for production use
deb http://download.proxmox.com/debian jessie pve-no-subscription

Best regards
Click to expand...

remove the non-existing pve repo:

> deb http://download.proxmox.com/debian jessie pve
 
hi,

new kernel does not include firmware for bnx2. look screen. after dist-upgrade + reboot, no network driver was available. we must install it with a usb drive. why firmware was not included?

missing-firmware.png

regards
 
hi, after upgrade i would add the node to cluster, but get following error message:
Code: 
unable to copy ssh ID
2 of 5 nodes works, 3 have this error. with ssh ip or ssh nodename i can connect to cluster

what can i do here?

regards


solved with: rm /root/.ssh/know_hosts
 
Last edited:
hi, how can i delete old openvz container? i have no button found.

old_openvz.png



solved with:
Code: 
rm -f /etc/pve/openvz/<ct-id>.conf
rm -R <storage-path>/private/*

regards
 
Last edited:
Trying to re-create cluster per the instructions and get this on the remote nodes:

pvecm add 10.7.40.151 -force
can't create shared ssh key database '/etc/pve/priv/authorized_keys'
cluster not ready - no quorum?
unable to add node: command failed (ssh 10.7.40.151 -o BatchMode=yes pvecm addnode proxmox02 --force 1)

Any assistance would be greatly appreciated, this is our production cluster and 3/4 of our VM's are DOA now.

Output on master node:
root@proxmox01:/etc/pve/nodes/proxmox01# pvecm status
Quorum information
------------------
Date: Sat Oct 10 15:52:14 2015
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 1148
Quorate: No


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


Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.7.40.151 (local)


One more note, I noticed my original cluster name was "Clusterfish" and I accidentally named the upgrade "clusterfish". Is a cluster name case sensitive?
 
Last edited:
dietmar said:
Why is expected votes set to 3 if you only have one node?
Click to expand...

I have no idea, I rebooted everything this morning and now get this:

root@proxmox01:~# pvecm status
Quorum information
------------------
Date: Sun Oct 11 08:16:31 2015
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 1168
Quorate: No


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


Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.7.40.151 (local)

Here's what I get when I try and force join the cluster from a freshly installed PVE4 host:

root@proxmox02:~# pvecm add 10.7.40.151 -force
can't create shared ssh key database '/etc/pve/priv/authorized_keys'
cluster not ready - no quorum?
unable to add node: command failed (ssh 10.7.40.151 -o BatchMode=yes pvecm addnode proxmox02 --force 1)
 
Sure, here it is:

root@proxmox01:/var/log/cluster# cat /etc/pve/corosync.conf
logging {
debug: off
to_syslog: yes
}


nodelist {
node {
nodeid: 4
quorum_votes: 1
ring0_addr: proxmox02
}


node {
nodeid: 3
quorum_votes: 1
ring0_addr: proxmox04
}


node {
nodeid: 2
quorum_votes: 1
ring0_addr: proxmox03
}


node {
nodeid: 1
quorum_votes: 1
ring0_addr: proxmox01
}


}


quorum {
provider: corosync_votequorum
}


totem {
cluster_name: Clusterfish
config_version: 4
ip_version: ipv4
secauth: on
version: 2
interface {
bindnetaddr: 10.7.40.151
ringnumber: 0
}


}
 
When taking snapshots, the hover text pretends to allow valid names like this:

Allowed characters: 'a-z', '0-9', '-', '_', '.'
Click to expand...

This leads me to try something like snapshot-2015-10-11, but then i get a warning:

Parameter verification failed. (400)

snapname: invalid format - invalid configuration ID 'snapshot-2015-10-11'
Click to expand...

Edit: I could'nt use things like 20151011 or 2015-10-11 either, this get's denied by javascript regex directly.

Edit2: Underscore works, it's ok for me, but then the "Allowed characters" is just wrong.
 
Last edited:
You must log in or register to reply here.
Top Bottom