Search results

I use Pandorafms has agents or u can do SNMP etc

Yes that would be a good option to have do live migration before reboot. We do that manually normally as we don't want any outage on the guest.

In 5.4 you can change the default action for reboot shutdown. You set this in datacenter options. By default reboot does not migrate and shutdown only migrates if the node takes longer than a minute to come back. You can change the default to fail over then it always will do that. Also make...

I simply have a template of the OS then clone it via the API. Then configure via API eg network disk size memory etc. all set cloud-int via API and start it It all works great

thanks for the info

Oh I remember now I had a problem with the networking I did a few things and fixed it In /etc/network/interfaces I removed Eth0 eth1 eth3 etc So then it only looks like this # This file describes the network interfaces available on your system # and how to activate them. For more...

Remove the second one that encodes the $data as I assume what u post to the APi maybe is also encoding it. Eg just try the one that encodes the key. And confirm. Everything use curl as a test then make u code do the same as curl is doing

you need to encode the key I guess in Python data["sshkeys"] =urllib.parse.urlencode(sshKey) then you encode data when you send to the API hence the key is double encoded

Interesting I did an update to the nodes from the pve-no-subscription and now it works as expected with the patch

After u patch u need to systemctl restart pvedaemon

yes systemctl restart pvedaemon

No not krbd remote ceph using MIMIC let me try and run some debug code and see if I can see what is happening I m away tomorrow though and it late here As I said the initial problem was fix with the patch as that error happened just with a normal start

Interesting I have external Ceph and both the Cloud-INIT and the VM drive on on ceph I did some more tests and still the same issue the VM is an Ubuntu one but it happens for all It Only happens if you do the HA start . Live or Shutdown migration works fine So if you create a VM then add...

I spoke too soon It works if the HA is not turned on If you add a VM to the HA then shutdown the VM and then issue start the error comes back It's almost like this code exists somewhere else if the VM is in HA mode. If you remove the VM from the HA and then restart it its ok ANY ideas ?

Yes also works for me

Install cloud init from buster wget http://ftp.us.debian.org/debian/pool/main/c/cloud-init/cloud-init_18.3-5_all.deb You need to install python3-jsonschema apt-get install python3-jsonschema dpkg -i cloud-init_18.3-5_all.deb rm the downloaded package rm cloud-init_18.3-5_all.deb it will...

Good that this is known :-) as I just got that during an upgrade from 5.3 to 5.4 rebooted the node they moved out and failed to start because task started by HA resource agent 2019-04-15 08:53:40.779470 7f4755195100 -1 did not load config file, using default settings. rbd: create error: (17)...

the bionic-server-cloudimg-amd64.img

My 18.04 still working originally from here. https://cloud-images.ubuntu.com

Check the xterm.js during boot. You can on me the output if needed