Activity log for bug #1800508

Date Who What changed Old value New value Message
2018-10-29 17:28:31 Wallace Cardoso bug added bug
2018-10-29 17:29:09 Wallace Cardoso attachment added Syslogs https://bugs.launchpad.net/nova/+bug/1800508/+attachment/5206824/+files/001.txt
2018-10-29 17:35:03 Wallace Cardoso description 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_instances, so the result would be the VM is in 'error' state. Steps to reproduce ===================== 1) Create a VM; 2) Inject an out-of-range value in 'schedule_and_build_instances/args/build_requests>nova_object.data/instance/nova_object.data/instance_type_id', this will be enough to cause a DBError. For instance, it can be used the 1E+22 value. 3) An exception will be thrown, but seems there no exist an appropriate action when this DBError happens. Expected result ================== The VM is put in 'error' state Actual result ================ The VM is in 'build' state indeterminately, and the user never will know (without searching in the logs) what happened with the VM. Environment ============== Devstack/Stable/Queens. Logs & Configs ================= Logs attached. 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_instances, so the result would be the VM is in 'error' state. Steps to reproduce ===================== 1) Create a VM; 2) Inject an out-of-range value in "schedule_and_build_instances.args.build_requests->'nova_object.data'.instance.'nova_object.data'.instance_type_id", this will be enough to cause a DBError. For instance, it can be used the 1E+22 value. 3) An exception will be thrown, but seems there no exist an appropriate action when this DBError happens. Expected result ================== The VM is put in 'error' state Actual result ================ The VM is in 'build' state indeterminately, and the user never will know (without searching in the logs) what happened with the VM. Environment ============== Devstack/Stable/Queens. Logs & Configs ================= Logs attached.
2018-10-29 17:39:07 Wallace Cardoso summary Missing exception handling mechanism in 'schedule_and_build_instances' for DBError at line 1180 Missing exception handling mechanism in 'schedule_and_build_instances' for DBError at line 1180 of nova/conductor/manager.py
2018-11-01 15:50:43 Matt Riedemann tags fault serviceability
2018-11-01 15:52:35 Matt Riedemann nova: importance Undecided Low
2018-11-01 15:53:46 Matt Riedemann nova: status New Triaged
2018-11-01 16:02:01 Matt Riedemann tags fault serviceability fault-injection serviceability
2018-11-01 16:02:16 Matt Riedemann nova: status Triaged Opinion