yahoo-eng-team team mailing list archive

[Wallace Felipe Francisco Cardoso <1799949@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===============
For the cases where an error occur inside the box of a component (nova-conductor, nova-compute, nova-scheduler), the system seems to handle the error putting the VM instance in the error state. But, earlier errors in the exchange between each component are not well handled as inside. I found that when an error occurs in the RPC server libs, for instance, when deserializing an object, the flow of creating the VM is not changed and stay forever building.

Steps to reproduce
=====================
1) Create a valid flavor (e.g. RAM=64mb, DISK=0, VCPUS=1);
2) Create a valid image (e.g. cirros);
3) Create the VM (i.e. the server) from the client of your preference with cells enabled;
4) Intercept the RPC call from nova-api to nova-conductor for the method 'schedule_and_build_instances';
5) Change the 'id' of "schedule_and_build_instances.args.build_requests->'nova_object.data'.id" parameter by a non-parseable value (e.g. None, '');
6) Waits for some seconds until the errors propagate on the system (i.e. possible to see in the logs of nova-conductor);

Expected result
==================
Based on the behavior of errors occurring in other circunstances, the VM state should be set to 'error', not building forever once an error was faced between nova-api and nova-conductor;

Actual result
================
VM state is 'build' forever

Environment
==============
I used the devstack to initialize all OpenStack components. This considers a basic installation in a single node. The version I have used is the Queens.

Logs & Configs
=================
Logs attached to this BugReport.

** Affects: nova
     Importance: Undecided
         Status: New

** Attachment added: "logs.txt"
   https://bugs.launchpad.net/bugs/1799949/+attachment/5205372/+files/logs.txt

-- 
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/1799949

Title:
  VM instance building forever when a RPC error occurs

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===============
  For the cases where an error occur inside the box of a component (nova-conductor, nova-compute, nova-scheduler), the system seems to handle the error putting the VM instance in the error state. But, earlier errors in the exchange between each component are not well handled as inside. I found that when an error occurs in the RPC server libs, for instance, when deserializing an object, the flow of creating the VM is not changed and stay forever building.

  Steps to reproduce
  =====================
  1) Create a valid flavor (e.g. RAM=64mb, DISK=0, VCPUS=1);
  2) Create a valid image (e.g. cirros);
  3) Create the VM (i.e. the server) from the client of your preference with cells enabled;
  4) Intercept the RPC call from nova-api to nova-conductor for the method 'schedule_and_build_instances';
  5) Change the 'id' of "schedule_and_build_instances.args.build_requests->'nova_object.data'.id" parameter by a non-parseable value (e.g. None, '');
  6) Waits for some seconds until the errors propagate on the system (i.e. possible to see in the logs of nova-conductor);

  Expected result
  ==================
  Based on the behavior of errors occurring in other circunstances, the VM state should be set to 'error', not building forever once an error was faced between nova-api and nova-conductor;

  Actual result
  ================
  VM state is 'build' forever

  Environment
  ==============
  I used the devstack to initialize all OpenStack components. This considers a basic installation in a single node. The version I have used is the Queens.

  Logs & Configs
  =================
  Logs attached to this BugReport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1799949/+subscriptions