Bug 1100369 - Puppet agent fails to run because fencing was off in common.pp file
Summary: Puppet agent fails to run because fencing was off in common.pp file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-foreman-installer
Version: 5.0 (RHEL 6)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ga
: 5.0 (RHEL 7)
Assignee: Jiri Stransky
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks: 1126445
TreeView+ depends on / blocked
 
Reported: 2014-05-22 16:42 UTC by Leonid Natapov
Modified: 2014-09-08 05:43 UTC (History)
8 users (show)

Fixed In Version: openstack-foreman-installer-2.0.3-1.el6ost
Doc Type: Bug Fix
Doc Text:
Prior to this update, a wait condition was present in a Puppet manifest for an event that does not occur when fencing is disabled. This resulted in an error when running the Puppet agent in deployments where fencing was disabled (typically proof-of-concept). With this update, the wait condition has been changed to an event that always occurs during deployment, regardless of fencing status. As a result, the Puppet agent runs successfully in conditions where fencing has been disabled.
Clone Of:
: 1126445 (view as bug list)
Environment:
Last Closed: 2014-08-04 18:33:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:1003 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2014-08-04 22:31:07 UTC

Description Leonid Natapov 2014-05-22 16:42:50 UTC 
If fencing is off in /usr/share/openstack-foreman-installer/puppet/modules/quickstack/manifests/pacemaker/common.pp file puppet agent fails with the following error:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find resource 'Exec[all-nodes-joined-cluster]' for relationship on 'Exec[pcs-resource-default]' on node puma42.scl.lab.tlv.redhat.com. Setting it to "on" solves the problem.
Comment 1 Jason Guiditta 2014-05-22 17:15:00 UTC 
Stonith disabled is not officially supported, so moving this to rhos5 to be fixed upstream and back ported as desired.
Comment 3 Jason Guiditta 2014-05-23 14:37:56 UTC 
Jirka posted a patch, now merged:

https://github.com/redhat-openstack/astapor/pull/236
Comment 9 errata-xmlrpc 2014-08-04 18:33:55 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.

http://rhn.redhat.com/errata/RHEA-2014-1003.html
Note You need to log in before you can comment on or make changes to this bug.