Bug 1745178

Summary:	nova notifications need to be enabled when novjoin is enabled
Product:	Red Hat OpenStack	Reporter:	Ade Lee <alee>
Component:	openstack-tripleo-heat-templates	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:	Pavan <pkesavar>
Severity:	high	Docs Contact:
Priority:	high
Version:	15.0 (Stein)	CC:	aschultz, ggrasza, hrybacki, kbasil, mburns, pkesavar
Target Milestone:	rc	Keywords:	Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-10.6.1-0.20190826150036.30390bc.el8ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:24:25 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 Ade Lee 2019-08-23 19:00:39 UTC

Description of problem:

Recently, a change was made to disable notifications when telemetry was disabled.
Unfortunately this does not account for novajoin-notifier, which listens to notifications from nova to be able to determine when servers are deleted so it can update IPA accordingly.
 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Grzegorz Grasza 2019-09-04 15:28:00 UTC

To verify this,
* deploy tripleo with "TLS everywhere"
* list hosts in IPA
* delete one of the overcloud openstack server instances
* lists hosts in IPA - the host should be removed
* there should be "Delete host ..." entry in novajoin-notifier logs, with info level

Alternatively, the whole deployment could be deleted - the hosts should also be removed from IPA.

Comment 11 errata-xmlrpc 2019-09-21 11:24:25 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, 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-2019:2811