Bug 1751413 - After deleting the stack the nodes are not deleted from IPA host
Summary: After deleting the stack the nodes are not deleted from IPA host
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-novajoin
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z12
: 13.0 (Queens)
Assignee: Ade Lee
QA Contact: Jeremy Agee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-11 23:43 UTC by chrisbro@redhat.com
Modified: 2023-10-06 18:36 UTC (History)
6 users (show)

Fixed In Version: python-novajoin-1.3.0-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-03 10:55:12 UTC
Target Upstream Version:
Embargoed:
chrisbro: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-1008 0 None None None 2023-10-06 18:36:36 UTC

Description chrisbro@redhat.com 2019-09-11 23:43:43 UTC
Description of problem:
After deleting the stack the nodes are not deleted from IPA host. 

Novajoin has been configured on the undercloud to assist with ipa host registration/cleanup of the overcloud nodes, when the overcloud stack is created/destroyed. However, we have been noticing inconsistency around ipa host clean up when the overcloud stack is deleted, in that the overcloud nodes still exist in the IPA server after the stack has been deleted. We would have expected that the IPA host entries would be completely removed when the overcloud stack has been deleted.

Version-Release number of selected component (if applicable):

Actual results:


Expected results:
Novajoin should clean up IPA when stack is deleted 

Additional info:

This is pretty much similar to BZ 1729451

Comment 19 Lon Hohberger 2020-03-11 10:36:33 UTC
According to our records, this should be resolved by python-novajoin-1.3.0-1.el7ost.  This build is available now.


Note You need to log in before you can comment on or make changes to this bug.