Public bug reported: I've got a patch:
https://review.openstack.org/#/c/426926/ That's trying to integrated the 'nova-status upgrade check' command into a grenade run, and it's failing here: http://logs.openstack.org/26/426926/2/check/gate-grenade-dsvm-neutron- ubuntu-xenial/8b536f3/logs/grenade.sh.txt.gz#_2017-01-30_22_20_29_466 It's failing because there is 1 compute node in the database (from the newton-side run of grenade) but no resource providers, which is because we're running the upgrade check after starting the placement service but before starting nova-compute with the upgraded ocata code, which is what gets that compute reporting into the placement service. I think this check is probably overly strict for Ocata given we will fallback to the compute_nodes table in the filter scheduler if not all computes are upgraded to ocata yet per this change: https://review.openstack.org/#/c/417961/ In Pike, the filter scheduler will not fallback to the compute_nodes table and will produce a NoValidHost error if there are no compute resource providers available. At that point, we could make the upgrade check more strict, but for now we probably just want this to be a warning or info level result for nova-status. ** Affects: nova Importance: High Assignee: Matt Riedemann (mriedem) Status: Triaged ** Tags: nova-status ocata-rc-potential upgrade ** Changed in: nova Assignee: (unassigned) => Matt Riedemann (mriedem) -- 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/1660484 Title: nova-status upgrade check fails if there are no computes reporting into placement Status in OpenStack Compute (nova): Triaged Bug description: I've got a patch: https://review.openstack.org/#/c/426926/ That's trying to integrated the 'nova-status upgrade check' command into a grenade run, and it's failing here: http://logs.openstack.org/26/426926/2/check/gate-grenade-dsvm-neutron- ubuntu-xenial/8b536f3/logs/grenade.sh.txt.gz#_2017-01-30_22_20_29_466 It's failing because there is 1 compute node in the database (from the newton-side run of grenade) but no resource providers, which is because we're running the upgrade check after starting the placement service but before starting nova-compute with the upgraded ocata code, which is what gets that compute reporting into the placement service. I think this check is probably overly strict for Ocata given we will fallback to the compute_nodes table in the filter scheduler if not all computes are upgraded to ocata yet per this change: https://review.openstack.org/#/c/417961/ In Pike, the filter scheduler will not fallback to the compute_nodes table and will produce a NoValidHost error if there are no compute resource providers available. At that point, we could make the upgrade check more strict, but for now we probably just want this to be a warning or info level result for nova-status. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1660484/+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
