Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1514060 - [Docs] OSP Installation and usage, section: 8.4. Replacing Controller Nodes -- should include a note about updating the fencing config
Summary: [Docs] OSP Installation and usage, section: 8.4. Replacing Controller Nodes -...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-16 15:13 UTC by Matt Flusche
Modified: 2019-04-12 05:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Matt Flusche 2017-11-16 15:13:16 UTC
Description of problem:
Doc: OSP Installation and usage, 
Section: 8.4. Replacing Controller Nodes

There should be notes in this section on updating the fencing/stonith pacemaker config. 

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Dan Macpherson 2018-08-07 06:20:43 UTC
I had a readthrough of the procedure and it looks like we're missing two things:

1. The user must configure fencing to accommodate the new node. You can xref to the following content:

2. The user needs to re-enable fencing (we disable it in the beginning).

So from the undercloud, the command to use is:

ssh heat-admin@ "sudo pcs property set stonith-enabled=true"

heat-admin@ is the controller node we originally disabled it on.

So we need an additional section on re-enabling fencing that accommodates these two items fencing.


Side note: For OSP 11+, we configure the fencing via director:

So we'll still need a fencing config section for OSP11+ but it must come before we run the "openstack overcloud deploy" command.

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