Description of problem: nova-consoleauth is being deprecated in Rocky [0], however it was kept in the product during Stein and fully removed in Train [1]. During the Controllers upgrade from OSP15 to OSP16, ther service should be fully removed (the container and service looks like it gets removed), but the service is still present in the CLI with the service being enabled and down: 2020-04-18 01:42:22 | [Waiting for compute services to be up] 2020-04-18 01:46:23 | FAILURE: Some compute services are down 2020-04-18 01:46:26 | +--------------------------------------+------------------+---------------------------+----------+---------+-------+----------------------------+ 2020-04-18 01:46:26 | | ID | Binary | Host | Zone | Status | State | Updated At | 2020-04-18 01:46:26 | +--------------------------------------+------------------+---------------------------+----------+---------+-------+----------------------------+ 2020-04-18 01:46:26 | | fb42a48d-0b3b-49ef-85c1-9dde83ab9c9c | nova-conductor | controller-0.redhat.local | internal | enabled | up | 2020-04-18T01:46:18.000000 | 2020-04-18 01:46:26 | | cf1f50fd-fa75-412a-838e-91c046384d99 | nova-consoleauth | controller-0.redhat.local | internal | enabled | down | 2020-04-18T01:26:40.000000 | 2020-04-18 01:46:26 | | b2661ad0-b92b-42c7-9ec0-b309a6318739 | nova-conductor | controller-1.redhat.local | internal | enabled | up | 2020-04-18T01:46:19.000000 | 2020-04-18 01:46:26 | | 0e99eea1-d057-4482-aad8-95d278a3c4e5 | nova-conductor | controller-2.redhat.local | internal | enabled | up | 2020-04-18T01:46:22.000000 | 2020-04-18 01:46:26 | | a569a5d7-b7c6-4a35-8385-3283d379c3d9 | nova-consoleauth | controller-1.redhat.local | internal | enabled | down | 2020-04-18T01:26:42.000000 | 2020-04-18 01:46:26 | | 6afc86ff-21fd-4ca2-a6ee-eadc02bcd8ac | nova-consoleauth | controller-2.redhat.local | internal | enabled | down | 2020-04-18T01:26:42.000000 | 2020-04-18 01:46:26 | | 36467f85-5344-41ed-aa5e-cb89ead20159 | nova-scheduler | controller-0.redhat.local | internal | enabled | up | 2020-04-18T01:46:24.000000 | 2020-04-18 01:46:26 | | ce919610-802b-417f-9daf-39beaa33048a | nova-scheduler | controller-1.redhat.local | internal | enabled | up | 2020-04-18T01:46:20.000000 | 2020-04-18 01:46:26 | | 162677d1-685b-43a3-abf6-7e68f1d23bd4 | nova-scheduler | controller-2.redhat.local | internal | enabled | up | 2020-04-18T01:46:20.000000 | 2020-04-18 01:46:26 | | 2396d58b-0f4e-4094-ac13-17fd6d3c0882 | nova-compute | compute-1.redhat.local | nova | enabled | up | 2020-04-18T01:46:21.000000 | 2020-04-18 01:46:26 | | 6abf8871-dded-4545-8426-40f6e19e8d32 | nova-compute | compute-0.redhat.local | nova | enabled | up | 2020-04-18T01:46:20.000000 | 2020-04-18 01:46:26 | +--------------------------------------+------------------+---------------------------+----------+---------+-------+----------------------------+ Logs: https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/DFG-upgrades-upgrade-upgrade-15-16.1_director-rhel-virthost-3cont_2comp_3ceph-ipv4-geneve-HA/10/ [0] - https://docs.openstack.org/releasenotes/nova/rocky.html#relnotes-18-0-3-stable-rocky-upgrade-notes [1] - https://review.opendev.org/#/c/658085/ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Run CI job https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/DFG-upgrades-upgrade-upgrade-15-16.1_director-rhel-virthost-3cont_2comp_3ceph-ipv4-geneve-HA/ 2. 3. Actual results: nova-consoleauth service, which is deprecated, appears as down and enabled Expected results: nova-consoleauth service not present. Additional info:
Since the state is listed as 'down', I suspect the service *did* get removed, but its entry in the Nova database has not been cleaned up. I'm not sure our upgrade automation should start deleting services, so I'd leave this as is and maybe add a blurb to the documentation that consoleauth can be manually deleted after an upgrade.
(In reply to Artom Lifshitz from comment #1) > Since the state is listed as 'down', I suspect the service *did* get > removed, but its entry in the Nova database has not been cleaned up. I'm not > sure our upgrade automation should start deleting services Discussed with the team - it should. > so I'd leave > this as is and maybe add a blurb to the documentation that consoleauth can > be manually deleted after an upgrade.
Just to give higher priority to this BZ, folks were reporting this issue also in the FFU procedure: https://bugzilla.redhat.com/show_bug.cgi?id=1853201
Could you please give an ETA on when would this issue be fixed? It's been triaged for some time already.
*** Bug 1853201 has been marked as a duplicate of this bug. ***
You could manually delete the nova-consoleauth service, until we have automated fix for this. ~~~ # source overcloudrc and execute below commands. openstack compute service list --service nova-consoleauth openstack compute service delete <service_id> ~~~
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1.8 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0986