Description of problem:
[Questions]Does NovaResumeGuestsStateOnHostBoot will change the instances to output virsh list --autostart ?
Version-Release number of selected component (if applicable):
16.2
How reproducible:
Steps to Reproduce:
1. create a yaml as the below
$ cat overcloud-customed-set/nova-gueststate.yaml
parameter_defaults:
NovaResumeGuestsStateOnHostBoot: True
2. deploy it with this template
3. The output of autostart not exist there
[root@rhosp16-compute0 ~]# podman exec -it nova_libvirt virsh list --autostart
Id Name State
--------------------
[root@rhosp16-compute0 ~]# podman exec -it nova_libvirt virsh list --no-autostart
Id Name State
-----------------------------------
1 instance-00000001 running
Actual results:
Couldn't get proper output and the instance also not comes up after compute reboot
Expected results:
The instance could reboot automatically after the compute node reboot
Additional info:
nova does not use livbirt autostart fucntionaltiy and NovaResumeGuestsStateOnHostBoot is not related to that.
we do not support auto start in our openstack product and do not plan to use it going forward.
I believe the no-support comment is for "virsh list --autostart" and "virsh list --no-autostart" integration of Nova and Libvirt.
Nova ensures the described functionality on its own, w/o relying nor using the libvirt autostart feature.
Hello, I have closed this bug as it has been waiting for more info for at least 4 weeks. We only do this to ensure that we don't accumulate stale bugs which can't be addressed. If you are able to provide the requested information, please feel free to re-open this bug.
Comment 20Red Hat Bugzilla
2024-08-15 04:25:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days