Reviewed: https://review.opendev.org/c/openstack/nova/+/898741 Committed: https://opendev.org/openstack/nova/commit/e1b84a398766bdbccf2d834364fc9e9a7547bb4a Submitter: "Zuul (22348)" Branch: master
commit e1b84a398766bdbccf2d834364fc9e9a7547bb4a Author: Dan Smith <[email protected]> Date: Wed Oct 18 07:23:29 2023 -0700 Revert "Add upgrade check for compute-object-ids linkage" This is being reverted because it's overly strict and complaining that upgrade-related work has not been done before it should have or needs to have been done. This may be re-added later when we start depending on these linkages. Closes-Bug: #2039597 This reverts commit 27f384b7ac4f19ffaf884d77484814a220b2d51d. Change-Id: Ifa5b82ca3b83d0ba481aa7a062827bd8e838989a ** Changed in: nova Status: In Progress => Fix Released -- 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/2039597 Title: nova-status upgrade check fails on Object ID linkage Status in OpenStack Compute (nova): Fix Released Bug description: Description =========== With upgrade from 2023.1 to 2023.2 when running nova-status upgrade check it fails with exit code 2. According to the documentation [1], this command was run with the new codebase (2023.2) but before any service (api/conductor/scheduler/compute) was restarted, so they still run on 2023.1 codebase. With that all computes are UP and healthy: # openstack compute service list +--------------------------------------+----------------+------+----------+---------+-------+----------------------------+ | ID | Binary | Host | Zone | Status | State | Updated At | +--------------------------------------+----------------+------+----------+---------+-------+----------------------------+ | 001ea1ce-363f-41d1-9ce3-59ff966452a7 | nova-conductor | aio1 | internal | enabled | up | 2023-10-17T18:14:38.000000 | | 8df25103-65c9-4892-be05-ebed7f3c1ad4 | nova-scheduler | aio1 | internal | enabled | up | 2023-10-17T18:14:40.000000 | | d85b115a-cd8a-4ac9-82bc-f7a5f457cedc | nova-compute | aio1 | nova | enabled | up | 2023-10-17T18:14:39.000000 | +--------------------------------------+----------------+------+----------+---------+-------+----------------------------+ Steps to reproduce ================== * Run cluster on 2023.1 * Perform upgrade to 2023.2 but do not restart nova services (as assumed by the documentation) * Run nova-status upgrade check Expected result =============== Upgrade check passes Actual result ============= +---------------------------------------------------------------------+ | Check: Object ID linkage | | Result: Failure | | Details: Compute node objects without service_id linkage were found | | in the database. Ensure all non-deleted compute services | | have started with upgraded code. | +---------------------------------------------------------------------+ 1] https://docs.openstack.org/nova/latest/cli/nova-status.html#upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2039597/+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
