Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1290268

Summary: rhel-osp-director: 7.1.->7.2 overcloud with external load balancer update has failed. The pacemaker stopped on one of the controllers during the update.
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: rhosp-directorAssignee: Giulio Fidente <gfidente>
Status: CLOSED ERRATA QA Contact: Alexander Chuzhoy <sasha>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: dmacpher, jcoufal, mburns, rhel-osp-director-maint
Target Milestone: y2Keywords: TestOnly, Triaged
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Pacemaker stopped working during Overcloud updates. This caused the updates to fail. This is fixed in a Pacemaker update for Red Hat Enterprise Linux 7.2. Now updates complete successfully without Pacemaker stopping.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-21 16:54:35 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:
Attachments:
Description Flags
logs from the controller where the pacemaker went down during the update.
none
logs from the controller where the update seems to pass and the pacemaker is up none

Description Alexander Chuzhoy 2015-12-10 00:01:45 UTC 
rhel-osp-director: 7.1.->7.2 overcloud with external load balancer update  has failed. The pacemaker stopped on one of the controllers during the update.

Environment:
instack-undercloud-2.1.2-34.el7ost.noarch
openstack-tripleo-0.0.7-0.1.1664e566.el7ost.noarch
openstack-tripleo-heat-templates-0.8.6-87.el7ost.noarch
openstack-tripleo-puppet-elements-0.0.1-5.el7ost.noarch
openstack-tripleo-common-0.0.1.dev6-5.git49b57eb.el7ost.noarch
openstack-tripleo-image-elements-0.9.6-10.el7ost.noarch


Steps to reproduce:

1. Deploy overcloud with external load balancer:
Deployment command:
openstack overcloud deploy --templates  -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml --control-scale 3 --compute-scale 1 --ntp-server x.x.x.x -e /usr/share/openstack-tripleo-heat-templates/environments/external-loadbalancer-vip.yaml -e external-lb.yaml

2. Update the deployment:
Update command:
openstack overcloud update stack overcloud -i --templates -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e  /usr/share/openstack-tripleo-heat-templates/environments/updates/update-from-vip.yaml -e network-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/external-loadbalancer-vip.yaml -e external-lb.yaml


Result:
The update fails in the middle.
Out of 3 controllers: first passed yum update, second passed yum update, but has the pacemaker stopped and third didn't even begin the yum update process.

Expected result:
The update should complete successfully.
Comment 1 Alexander Chuzhoy 2015-12-10 00:04:32 UTC 
Created attachment 1104200 [details]
logs from the  controller where the pacemaker went down during the update.
Comment 2 Alexander Chuzhoy 2015-12-10 00:07:44 UTC 
Created attachment 1104201 [details]
logs from the  controller where the update seems to pass and the pacemaker is up
Comment 4 Alexander Chuzhoy 2015-12-11 17:22:22 UTC 
Verified.


Was able to successfully update an overcloud with external lb from 7.1 to 7.2.
Comment 6 errata-xmlrpc 2015-12-21 16:54:35 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/RHBA-2015:2651