First I must say I’m pretty new here so it is very possible the problem here is something I’ve done.
Lately I’ve been having some trouble with the vmpool.info function (specifically I’m using pyone).
I’m running tests that look for a VM in opennebula by name and sometimes the function one.vmpool.info can’t find the VMs even though I can see they exist and running at the time.
The exact command I’m running is
one.vmpool.info(-2, -1, -1, -1, "name="test-vm")
I also have exact logs I save from a month ago that show the vm I am talking about and the command I ran (it happened many times since then, that’s just the log I have at hand):
323762.log - log of the vm to search (speciffically note that the VM is running at 05:56:56)
Thu Feb 15 05:56:50 2024 [Z0][VM][I]: New state is ACTIVE
Thu Feb 15 05:56:50 2024 [Z0][VM][I]: New LCM state is PROLOG
Thu Feb 15 05:56:51 2024 [Z0][VM][I]: New LCM state is BOOT
Thu Feb 15 05:56:51 2024 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/323762/deployment.0
Thu Feb 15 05:56:51 2024 [Z0][VM][I]: Virtual Machine has no context
Thu Feb 15 05:56:51 2024 [Z0][VMM][I]: Succesfully execute network driver operation: pre.
Thu Feb 15 05:56:51 2024 [Z0][VMM][I]: ExitCode: 0
Thu Feb 15 05:56:51 2024 [Z0][VMM][I]: Succesfully execute virtualization driver operation: /bin/mkdir -p.
Thu Feb 15 05:56:51 2024 [Z0][VMM][I]: ExitCode: 0
Thu Feb 15 05:56:51 2024 [Z0][VMM][I]: Succesfully execute virtualization driver operation: /bin/cat - >/var/lib/one//datastore/102/323762/vm.xml.
Thu Feb 15 05:56:51 2024 [Z0][VMM][I]: ExitCode: 0
Thu Feb 15 05:56:51 2024 [Z0][VMM][I]: Succesfully execute virtualization driver operation: /bin/cat - >/var/lib/one//datastore/102/323762/ds.xml.
Thu Feb 15 05:56:53 2024 [Z0][VMM][I]: ExitCode: 0
Thu Feb 15 05:56:53 2024 [Z0][VMM][I]: Succesfully execute virtualization driver operation: deploy.
Thu Feb 15 05:56:53 2024 [Z0][VMM][I]: Succesfully execute network driver operation: post.
Thu Feb 15 05:56:53 2024 [Z0][VM][I]: New LCM state is RUNNING
Thu Feb 15 05:56:57 2024 [Z0][VM][I]: New LCM state is SHUTDOWN
Thu Feb 15 05:56:59 2024 [Z0][VMM][I]: ExitCode: 0
Thu Feb 15 05:56:59 2024 [Z0][VMM][I]: Successfully execute virtualization driver operation: cancel.
Thu Feb 15 05:56:59 2024 [Z0][VMM][I]: Successfully execute network driver operaion: clean.
Thu Feb 15 05:56:59 2024 [Z0][VM][I]: New LCM state is EPILOG
Thu Feb 15 05:56:59 2024 [Z0][VM][I]: New state is DONE
Thu Feb 15 05:56:59 2024 [Z0][VM][I]: New LCM state is LCM_INIT
oned.log - log of the commands ran on opennebula to get the vm
Thu Feb 15 05:56:56 2024 [Z0][ReM][D]: Req:7344 UID:0 IP:1.2.3.4 one.vmpool.info.invoked , -2, -1, -1, -1, "name=test-vm"
Thu Feb 15 05:56:56 2024 [Z0][ReM][D]: Req:7344 UID:0 one.vmpool.info result SUCCESS, "<VM_POOL></VM_POOL>"
As can be seen the one.vmpool.info did not return “test-vm” even though is existed at the time of the search and was running.
For referance this happend approximetly 1 in 100 times which is pretty
Any help I can get on why this is happening or how to fix it will be hugely appreciated.
I’m running version 6.4.0 so this might be the problem but I couldn’t find anything in the changelog that address this.
