Bug 1324582

Summary: rhel-osp-director: Fence agent is disabled after upgrade 7.3 ->8.0
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: documentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: dbecker, dmacpher, mburns, morazi, rhel-osp-director-maint, sasha, srevivo
Target Milestone: gaKeywords: Documentation
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-03 14:23:55 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:

Description Alexander Chuzhoy 2016-04-06 17:11:53 UTC 
rhel-osp-director: Fence agent is disabled after upgrade 7.3 ->8.0


Environment:
libxshmfence-1.2-1.el7.x86_64
instack-undercloud-2.2.7-2.el7ost.noarch
openstack-tripleo-heat-templates-0.8.14-5.el7ost.noarch
openstack-puppet-modules-7.0.17-1.el7ost.noarch
openstack-tripleo-heat-templates-kilo-0.8.14-5.el7ost.noarch


Steps to reproduce:
1. Deploy overcloud 7.3 and configure/test fencing.
2. Upgrade the setup to 8.0
3. Run "pcs property show"

Result:
Cluster Properties:
 cluster-infrastructure: corosync
 cluster-name: tripleo_cluster
 dc-version: 1.1.13-10.el7_2.2-44eb2dd
 have-watchdog: false
 last-lrm-refresh: 1459895202
 maintenance-mode: false
 redis_REPL_INFO: overcloud-controller-2
 stonith-enabled: false
Node Attributes:
 overcloud-controller-0: rmq-node-attr-last-known-rabbitmq=rabbit@overcloud-controller-0
 overcloud-controller-1: rmq-node-attr-last-known-rabbitmq=rabbit@overcloud-controller-1
 overcloud-controller-2: rmq-node-attr-last-known-rabbitmq=rabbit@overcloud-controller-2

Expected result:
[root@overcloud-controller-2 ~]# pcs property show
Cluster Properties:
 cluster-infrastructure: corosync
 cluster-name: tripleo_cluster
 dc-version: 1.1.13-10.el7_2.2-44eb2dd
 have-watchdog: false
 last-lrm-refresh: 1459895202
 maintenance-mode: false
 redis_REPL_INFO: overcloud-controller-2
 stonith-enabled: true
Node Attributes:
 overcloud-controller-0: rmq-node-attr-last-known-rabbitmq=rabbit@overcloud-controller-0
 overcloud-controller-1: rmq-node-attr-last-known-rabbitmq=rabbit@overcloud-controller-1
 overcloud-controller-2: rmq-node-attr-last-known-rabbitmq=rabbit@overcloud-controller-2



Note: once the user runs "pcs property set stonith-enabled=true", this is fixed.
Comment 2 Mike Burns 2016-04-06 17:31:55 UTC 
basically a duplicate of bug 1289517.  We should add additional docs to the upgrade section until we have automated config of fencing.
Comment 4 Dan Macpherson 2016-05-03 02:10:16 UTC 
Notes have been published as part of th Overcloud upgrade process, include the note about re-enabling stonith:

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

===
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
===

Sasha, was there anything else I should add for this note?