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

Bug 1283561

Summary: Pacemaker stop actions timing out during yum update on the overcloud
Product: Red Hat OpenStack Reporter: Jiri Stransky <jstransk>
Component: rhosp-directorAssignee: Jiri Stransky <jstransk>
Status: CLOSED ERRATA QA Contact: Leonid Natapov <lnatapov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: dmacpher, jcoufal, jslagle, jstransk, mburns, ohochman, rhel-osp-director-maint
Target Milestone: y2   
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-0.8.6-78.el7ost Doc Type: Bug Fix
Doc Text:
Strict timeouts on starting and stopping services through Pacemaker caused updates to fail. This fix increases the timeouts for starting and stopping services through Pacemaker. Now services start and stop within the timeout limit and the Overcloud now succeeds.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-21 16:54:14 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 Jiri Stransky 2015-11-19 10:03:35 UTC
We've seen various failures during yum update on the overcloud, mostly services timing out. The timeouts need to be increased. This is one of the prerequisites to having updates working properly.

Comment 2 Udi Shkalim 2015-11-22 15:54:04 UTC
Hi Jiri,

Can you please provide steps to reproduce or verification process.

Thanks,
Udi

Comment 4 Leonid Natapov 2015-12-08 14:10:58 UTC
Update from ospd 7.1 to ospd 7.2 was successful.

Comment 6 errata-xmlrpc 2015-12-21 16:54:14 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