Bug 1613847

Summary:	dedicated monitor node scale up or monitor replacement causes stack update to fail and takes monitors out of quorum
Product:	Red Hat OpenStack	Reporter:	John Fulton <johfulto>
Component:	openstack-tripleo-heat-templates	Assignee:	John Fulton <johfulto>
Status:	CLOSED ERRATA	QA Contact:	Yogev Rabl <yrabl>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	14.0 (Rocky)	CC:	adeza, ahrechan, anharris, aschoen, ceph-eng-bugs, gamado, gfidente, gmeno, johfulto, jschluet, kdreyer, mariel, mburns, nthomas, ohochman, sankarshan, sclewis, scohen, slinaber, yrabl
Target Milestone:	beta	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-9.0.0-0.20181001174824.90afd18.0rc2.0rc2.0rc2.el7ost openstack-tripleo-common-9.4.1-0.20181002162541.5a9c7aa.el7ost	Doc Type:	Bug Fix
Doc Text:	Dedicated monitor node scale-up or monitor replacement no longer causes the `stack update` command to fail or to take Ceph monitors out of quorum.	Story Points:	---
Clone Of:	1548026	Environment:
Last Closed:	2019-01-11 11:51:11 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:

Comment 2 John Fulton 2018-08-08 12:09:33 UTC

WHY is this a OSP14 clone of an OSP13 bug if the fix would have been made upstream first?

Bug #1548026 and it's patch (https://review.openstack.org/#/c/567782) only resolves the symptoms described in this bug for OSP13 where Mistral runs ceph-ansible. This bug and it's change (https://review.openstack.org/#/c/582811) only resolves the symptoms of this bug when using config-download. Same solution, different implementation.

Comment 11 Gal Amado 2018-11-15 14:58:09 UTC

verified with core_puddle=2018-11-07.2

covered by automation.

Comment 14 errata-xmlrpc 2019-01-11 11:51:11 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:0045