Bug 1327717 - documentation: several slight corrections to controller replacement procedure.
Summary: documentation: several slight corrections to controller replacement procedure.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 18:01 UTC by Alexander Chuzhoy
Modified: 2016-06-16 04:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-16 04:40:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexander Chuzhoy 2016-04-15 18:01:20 UTC
documentation: several slight corrections to controller replacement procedure.

https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/director-installation-and-usage/810-scaling-the-overcloud


1)

Step 6
Log in to each Controller node, remove the failed node from /etc/corosync/corosync.conf, and restart Corosync. For example, to remove the failed node from Controller node 0's configuration: 

Ends with: " Complete this on each node. "

Should be replaced with " Complete this on each controller node. "


2)
Step 7
 Start Pacemaker and Corosync on the new node
Should be replaced with:
 Start Pacemaker and Corosync on the new node from a remaining controller node.


3)
Step 8
 Enable and restart the keystone service through Pacemaker:

[heat-admin@overcloud-controller-3 ~]$ sudo pcs resource enable openstack-keystone-clone overcloud-controller-3

To add a note about disregarding the warnings maybe:
"Warning: 'openstack-keystone' is unmanaged                                                                     
Warning: 'openstack-keystone-clone' is unmanaged "

Comment 3 Alexander Chuzhoy 2016-05-07 05:12:27 UTC
Verified:
Looks good

Comment 4 Dan Macpherson 2016-06-16 04:40:55 UTC
Changes now live on the customer portal.


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