Bug 1732955
Summary: | Unable to delete nova-cert service on OSP13 | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Matt Flusche <mflusche> |
Component: | openstack-nova | Assignee: | melanie witt <mwitt> |
Status: | CLOSED CANTFIX | QA Contact: | OSP DFG:Compute <osp-dfg-compute> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 13.0 (Queens) | CC: | dasmith, eglynn, jhakimra, kchamart, mschuppe, mwitt, pamadio, sbauza, sgordon, vromanso |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-07-30 06:53:02 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: |
Description
Matt Flusche
2019-07-24 20:10:18 UTC
The nova-cert service was removed from the codebase during the Pike release: https://blueprints.launchpad.net/nova/+spec/remove-nova-cert and in Queens, the versioned notifications code began using an enumerated value for the possible notification source services: https://github.com/openstack/nova/blob/17.0.0/nova/objects/fields.py#L797-L816 and the nova-cert service was not included as it had already been removed. Because the nova-cert service is not in the expected enumerated values, the notification object code blows up. Note: This is related to BZ1716025 where we work to disable nova-cert on the undercloud with a minor update before doing the ffu. Needs a KBase to document manual database manipulation to remove traces of nova-cert. SME: Martin / Mel. A way to remove the nova-cert service in OSP13 is documented in [1]. A fix to remove the service on a minor OSP10 update is tracked in BZ1716025. Closing this with CANTFIX and the documented workaround in [1] [1] https://access.redhat.com/solutions/4260191 |