Bug 1971056

Summary: [OSP 17] After host reboot VM goes to error state due to nova-compute EmptyCatalog error
Product: Red Hat OpenStack Reporter: Matthew Secaur <msecaur>
Component: openstack-novaAssignee: Lee Yarwood <lyarwood>
Status: CLOSED ERRATA QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: dasmith, eglynn, jhakimra, kchamart, lyarwood, sbauza, sgordon, vromanso
Target Milestone: betaKeywords: Patch, Triaged
Target Release: 17.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-nova-23.0.3-0.20210908140341.e39bbdc.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1972706 (view as bug list) Environment:
Last Closed: 2022-09-21 12:15:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1972706, 1979850    

Description Matthew Secaur 2021-06-11 18:49:24 UTC
Description of problem:
When a host is rebooted with a LUKSv1 encrypted volume, the instance will fail with the error:

Failure attaching encryptor; rolling back volume connection: keystoneauth1.exceptions.catalog.EmptyCatalog: The service catalog is empty.

Version-Release number of selected component (if applicable):
openstack-nova-compute-20.4.1-1.20201114041747.el8ost.noarch.rpm
openstack-nova-common-20.4.1-1.20201114041747.el8ost.noarch.rpm


How reproducible:
Reboot node using LUKs volume

Actual results:
Instance goes into ERROR state

Expected results:
Instance should boot normally

Additional info:
Barbican is in use in the environment

Comment 1 Matthew Secaur 2021-06-11 18:57:42 UTC
The version of Nova in use already includes the fixes from BZ 1905016 (errata RHBA-2021:0817). 

This issues appears to be related to upstream bug https://bugs.launchpad.net/nova/+bug/1905701

That upstream bug is fixed in openstack-nova-23.

Requesting that this upstream bug be backported to OSP16.1.

Comment 2 Matthew Secaur 2021-06-11 19:21:30 UTC
I just learned that the customer manually applied the change in this upstream bug [1] and it resolved the issue.

So it looks like we just need a backport of that piece of code to OSP16.1.

[1] https://review.opendev.org/c/openstack/nova/+/793463

Comment 14 errata-xmlrpc 2022-09-21 12:15:48 UTC
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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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/RHEA-2022:6543