Bug 1283561 - Pacemaker stop actions timing out during yum update on the overcloud
Summary: Pacemaker stop actions timing out during yum update on the overcloud
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: y2
: 7.0 (Kilo)
Assignee: Jiri Stransky
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-19 10:03 UTC by Jiri Stransky
Modified: 2015-12-21 16:54 UTC (History)
7 users (show)

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.
Clone Of:
Environment:
Last Closed: 2015-12-21 16:54:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 244321 0 None None None Never
OpenStack gerrit 244322 0 None None None Never
OpenStack gerrit 245174 0 None None None Never
OpenStack gerrit 247184 0 None None None Never
Red Hat Product Errata RHBA-2015:2651 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OSP 7 director Bug Fix Advisory 2015-12-21 21:50:26 UTC

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
Note You need to log in before you can comment on or make changes to this bug.