A few months ago, I saw a duplicate of the root cause of this issue downstream [1] where a failure during _set_vm_state_and_notify (example: MessagingTimeout) prevents us from setting the cell_id for an InstanceMapping and destroying the BuildRequest.
The InstanceMapping cell_id part of it was solved (from an MQ failure perspective) by a patch that landed in Ussuri: https://review.opendev.org/683730 and I think this is the root cause of the problem described in this bug. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1848737#c1 ** Bug watch added: Red Hat Bugzilla #1848737 https://bugzilla.redhat.com/show_bug.cgi?id=1848737 ** Also affects: nova/rocky Importance: Undecided Status: New ** Also affects: nova/train Importance: Undecided Status: New ** Also affects: nova/pike Importance: Undecided Status: New ** Also affects: nova/stein Importance: Undecided Status: New ** Also affects: nova/queens 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/1775934 Title: Cannot run "openstack server list" with instance stuck in scheduling state Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) pike series: New Status in OpenStack Compute (nova) queens series: New Status in OpenStack Compute (nova) rocky series: New Status in OpenStack Compute (nova) stein series: New Status in OpenStack Compute (nova) train series: In Progress Bug description: Seeing this in Ocata at 125dd1f30fdaf50182256c56808a5199856383c7. Running `openstack server list --project 9c28d07207a54c78848fd7b4f85779d5` results in a 500 error: RESP BODY: {"computeFault": {"message": "Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.\n<class 'nova.exception.InstanceNotFound'>", "code": 500}} Traceback in nova-api: http://paste.openstack.org/show/6YrSmjMSo0lIxyFjbPIz/ some data on the instance: http://paste.openstack.org/show/6PSa35HvdxZCQnVQ2sQU/ Looks like lazy-loading the flavor is failing because it's looking in the wrong database. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1775934/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
