Bug 1292035

Summary:	Add stonith bug to rhel osp director upgrade process document
Product:	Red Hat OpenStack	Reporter:	Ofer Blaut <oblaut>
Component:	documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	adahms, dmacpher, oblaut, yeylon
Target Milestone:	async	Keywords:	Documentation, Reopened, UserExperience
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-13 04:43:44 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 Ofer Blaut 2015-12-16 09:53:05 UTC

Description of problem:


I would like to add bug [1] into the upgrade process 

stonith is shutdown after upgrade [1], the upgrade will success, but customer might miss that release note, which will put his system in risky mode.


[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1289517
 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dan Macpherson 2015-12-17 06:02:55 UTC

Committed: https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Linux_OpenStack_Platform/commit/f3cddc75c05697538343f6595c1a135485a44ecf

Note is at the end of the upgrade process and says the following:

== IMPORTANT ==
If you configured fencing for your Controller nodes, the update process might disable it. When the update process completes, reenable fencing with the following command on one of the Controller nodes:

$ sudo pcs property set stonith-enabled=true
===

Ofer, how does that sound to you?

Comment 2 Dan Macpherson 2016-01-25 01:38:57 UTC

Ofer, just following up on this bug. This should no be published live. Was there anything further required for this bug?

Comment 3 Dan Macpherson 2016-03-01 01:23:18 UTC

No response in over a month. Closing this BZ. If changes are required, feel free to reopen.

Comment 6 Ofer Blaut 2016-03-06 13:51:39 UTC

Checked the doc 

Thanks

Ofer

Comment 7 Andrew Dahms 2016-04-13 04:43:44 UTC

This content is now live on the Customer Portal.

Closing.