[Yahoo-eng-team] [Bug 1813223] [NEW] "Requested operation is not valid: domain is not running" (REBUILD)

Public bug reported: I'm not sure if I can do these steps in practice, but I could perform the following steps in the system, and I got the an error. DevStack branch=stable/rocky. 1. ./unstack.sh && ./clean.sh && ./stack.sh 2. source openrc admin admin 3. openstack flavor create --ram 21 --di

[Yahoo-eng-team] [Bug 1804205] [NEW] libvirtError: operation failed: domain 'instance-00000003' already exists with uuid e017717e-9647-4740-8efa-4ec2aa25f35c

Public bug reported: Description == Testing the Nova component, I figured out that many times the instances (servers) were not created or instantiated because the following error: libvirtError: operation failed: domain 'instance-0003' already exists with uuid e017717e-9647-4740-8

[Yahoo-eng-team] [Bug 1801733] [NEW] nova-compute consuming 100% of cpu after rebuilding with invalid data parameters

Public bug reported: Description == The 'conductor-api' for 'rebuild_instance' has a vulnerability point for the parameter 'rebuild_instance/args/instance/nova_object.data/flavor/nova_object.data/vcpus'. When set to an invalid number of vcpus in the flavor of the instance, the comp

[Yahoo-eng-team] [Bug 1800508] [NEW] Missing exception handling mechanism in 'schedule_and_build_instances' for DBError at line 1180

Public bug reported: Description == If an error occurs during instance creation, the user won't be able to know what exactly happened with the VM that remains always building. As usual, the workflow of creating a VM was interrupted by an exception in the method schedule_and_build_in

[Yahoo-eng-team] [Bug 1800204] [NEW] n-cpu.service consuming 100% of CPU indeterminately

Public bug reported: Description == I used fault injection to assess the robustness of the nova-conductor, and by injecting a specific sequence of failures I saw a failure that can threaten the robustness of the system. The resulting of applying these faults in the interface of nova