Public bug reported: Description =========== After stopping the nova-compute service on a node, powering on VMs that were in a shutoff state, but assigned to the compute node where the compute service is no longer running, are powered on the host where the nova-compute service is stopped, causing the VM task state to be set to a bad state of "powering-on" forever.
Steps to reproduce ================== Example: Disable the nova-compute service on host compute001 VM001 was previously running on this host, but is now shut down Power on VM001 nova-scheduler schedules VM001 on compute001 Expected result =============== The scheduler filter ComputeFilter should see that compute001 is not "operational and enabled", as described here: https://docs.openstack.org/ocata/config-reference/compute/schedulers.html#computefilter and "not" schedule this VM on host compute001. Actual result ============= compute001 is chosen to power on VM001, leaving it in a bad task state of "powering-on" forever. Environment =========== stable/rocky using Kolla-Ansible 7.0.0.0rc3devXX and Kolla 7.0.0.0rc3devXX. CentOS 7.5 with latest updates Kernel: Linux 4.18.14-1.el7.elrepo.x86_64 Hypervisor: KVM Storage: Ceph Networking: DVR ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1798805 Title: Nova scheduler schedules VMs on nodes where nova-compute is down Status in OpenStack Compute (nova): New Bug description: Description =========== After stopping the nova-compute service on a node, powering on VMs that were in a shutoff state, but assigned to the compute node where the compute service is no longer running, are powered on the host where the nova-compute service is stopped, causing the VM task state to be set to a bad state of "powering-on" forever. Steps to reproduce ================== Example: Disable the nova-compute service on host compute001 VM001 was previously running on this host, but is now shut down Power on VM001 nova-scheduler schedules VM001 on compute001 Expected result =============== The scheduler filter ComputeFilter should see that compute001 is not "operational and enabled", as described here: https://docs.openstack.org/ocata/config-reference/compute/schedulers.html#computefilter and "not" schedule this VM on host compute001. Actual result ============= compute001 is chosen to power on VM001, leaving it in a bad task state of "powering-on" forever. Environment =========== stable/rocky using Kolla-Ansible 7.0.0.0rc3devXX and Kolla 7.0.0.0rc3devXX. CentOS 7.5 with latest updates Kernel: Linux 4.18.14-1.el7.elrepo.x86_64 Hypervisor: KVM Storage: Ceph Networking: DVR To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1798805/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
