Public bug reported: In Ocata, nova-compute wouldn't start if placement wasn't available, but it didn't check the version so placement from newton will still work with ocata computes. Also, the filter scheduler will fallback to not using placement if the computes aren't all new enough yet, but even once the computes are upgraded if placement is not the latest and microversion 1.4 isn't available, then the filter scheduler will not find any resource providers and it will result in a NoValidHost error.
For Pike, the fallback code for the older computes has been removed from the filter scheduler: https://review.openstack.org/#/c/436180/ So we're always calling placement from the filter scheduler. However, we don't enforce a minimum version of placement and we need 1.4 for the filter scheduler to work. We should add a check to the "nova-status upgrade check" command to enforce that placement is running with at least the 1.4 microversion (ocata) before upgrading to Pike. ** Affects: nova Importance: High Status: Confirmed ** Tags: nova-status placement scheduler upgrade -- 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/1669433 Title: nova-status needs to check that placement 1.4 is available for pike Status in OpenStack Compute (nova): Confirmed Bug description: In Ocata, nova-compute wouldn't start if placement wasn't available, but it didn't check the version so placement from newton will still work with ocata computes. Also, the filter scheduler will fallback to not using placement if the computes aren't all new enough yet, but even once the computes are upgraded if placement is not the latest and microversion 1.4 isn't available, then the filter scheduler will not find any resource providers and it will result in a NoValidHost error. For Pike, the fallback code for the older computes has been removed from the filter scheduler: https://review.openstack.org/#/c/436180/ So we're always calling placement from the filter scheduler. However, we don't enforce a minimum version of placement and we need 1.4 for the filter scheduler to work. We should add a check to the "nova- status upgrade check" command to enforce that placement is running with at least the 1.4 microversion (ocata) before upgrading to Pike. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1669433/+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
