Public bug reported: As reported on the mailing list:
http://lists.openstack.org/pipermail/openstack- discuss/2022-January/026603.html The service version check at startup can prevent FFUs from being possible without hacking the database. As implemented here: https://review.opendev.org/c/openstack/nova/+/738482 We currently filter "forced down" computes from the check, but we should probably also eliminate those down long enough due to missed heartbeats (i.e. offline during the upgrade). However, a fast-moving FFU where everything is switched from an old container to a new one would easily still find computes that are considered "up" and effectively force a wait. ** Affects: nova 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/1958883 Title: Service version check breaks FFU Status in OpenStack Compute (nova): New Bug description: As reported on the mailing list: http://lists.openstack.org/pipermail/openstack- discuss/2022-January/026603.html The service version check at startup can prevent FFUs from being possible without hacking the database. As implemented here: https://review.opendev.org/c/openstack/nova/+/738482 We currently filter "forced down" computes from the check, but we should probably also eliminate those down long enough due to missed heartbeats (i.e. offline during the upgrade). However, a fast-moving FFU where everything is switched from an old container to a new one would easily still find computes that are considered "up" and effectively force a wait. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1958883/+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
