Switching to invalid as incomplete is not a closed state. ** Changed in: nova Status: Incomplete => Invalid
-- 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/1431291 Title: Scheduler Failures are no longer logged with enough detail for a site admin to do problem determination Status in OpenStack Compute (nova): Invalid Bug description: After the move of the scheduler dispatch into conductor all the logging changed. The impact is that the scheduler no longer logs scheduled failures at WARN in the scheduler log with the instance id in question. (This apparently also somehow slipped back into Juno) This is a notable regression from an ops perspective, and has required everyone to start running debug and doing lots of log searching to figure out whats going on. The ops community asked that we log at a high level (WARN seems appropriate here) with reason, context, and instance id which makes their problem determination loop on "nova didn't boot my thing" from users much quicker. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1431291/+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