Search results

I want to consider our current cluster - 3 nodes for implementing VLAN while it is live. This is a critical cluster contain PROD environment. I want to do this without impact or down time. current the interface file looks like this: auto lo iface lo inet loopback iface enp3s0 inet manual...

Do you mind telling me exactly how that can be done? Thanks,...

Thanks but that means downtime which we cannot afford to do at this time. I was thinking why not create pve LVM group That idea is good but not at this time. We don't want to have to keep doing that. I am going to rebuild the node using ext4 LVM this time. That way there no problem

I have an issue were the host I am migrating to has ZFS on it instead of EXT4 and the VM was build using LVM. 020-03-09 18:50:19 starting migration of VM 132 to node 'host10' (xxx.xxx.xxx.21) 2020-03-09 18:50:19 found local disk 'local-lvm:vm-132-disk-1' (via storage) 2020-03-09 18:50:19 found...

Has anyone written a STEP by STEP of how to using LDAP NOT A/D on Proxmox

Out of Frustration, I rebuild all 3 node, You instructions is further confusing. Because I ran update then dist-upgrade which is covered in many documentation. Why full-upgrade?

I end up resolving the issue, by coping corosync to all 3 nodes then restarting corosync. very frustrating....

Doesn't the version have to be changed as well? I believe corosyc expects this which similar to making DNS changes. totem { cluster_name: clu3 config_version: 3 <----- This needs to be changed?

rebooting all 3 nodes did not fix this: host19:~# pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve) pve-manager: 6.1-3 (running version: 6.1-3/37248ce6) pve-kernel-5.3: 6.0-12 pve-kernel-helper: 6.0-12 pve-kernel-5.3.10-1-pve: 5.3.10-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync...

I just built this cluster. I get the following error: root@host19:~# pvecm status Can't use an undefined value as a HASH reference at /usr/share/perl5/PVE/CLI/pvecm.pm line 462, <DATA> line 755. root@host19:~# I am going to reboot the nodes to see if this occurs again.

host21:~# systemctl status pveproxy.service ● pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled) Active: activating (start-pre) since Wed 2020-03-04 20:49:31 PST; 111ms ago Cntrl PID: 7057 (pvecm) Tasks: 1...

Hi, I got the following error after doing dist-upgrade on my node. rrors were encountered while processing: pve-manager E: Sub-process /usr/bin/dpkg returned an error code (1) I rebooted the node and re-run this again: Do you want to continue? [Y/n] y Setting up pve-manager (6.1-7) ...

I appreciate the links and info, but I am trying to reach the vendor itself to understand terraform requirement for proxmox versions. I really need to see that they support version 6.1.x. Very import...

Is Terraform supported on proxmox 6.1? If so what are the requirements?

Can I get 5.3x versions? If so where?

There specific code versions of software that include Terraform v0.12.0 Do you have a supported version of proxmox other than 5.3 or 5.4? Could 6.x work?

Thanks, let me see if proxmox has it where I can get it first. I appreciate the offer.

do pveversion -v As you see i have pve-manager 5.3.5 not 5.4.x roxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve) pve-manager: 5.3-5 (running version: 5.3-5/97ae681d) pve-kernel-4.15: 5.2-12 pve-kernel-4.15.18-9-pve: 4.15.18-30 This why I want to know how to get 5.3 version... Phillip

Sounds like what needed is to add cluster-id info or at least look at corosync to do that so VM's know the difference. What you have is dangerous to production environment. So this means for time being best practice that each cluster has it OWN NFS volume.

I download 5.4. and got 5.4.5 is there any way to get 5.4.3. The reason is we have current cluster that using this specific versions. I have installed 5.4.5 on new nodes that I plan to add to an existing cluster and cannot upgrade the existing cluster due to existing cluster and cannot afford...