Bug 1100369
| Summary: | Puppet agent fails to run because fencing was off in common.pp file | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Leonid Natapov <lnatapov> | |
| Component: | openstack-foreman-installer | Assignee: | Jiri Stransky <jstransk> | |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 5.0 (RHEL 6) | CC: | jguiditt, jstransk, mburns, mlopes, morazi, rhos-maint, sclewis, yeylon | |
| Target Milestone: | ga | Keywords: | ZStream | |
| Target Release: | 5.0 (RHEL 7) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1126445 (view as bug list) | Environment: | ||
| Last Closed: | 2014-08-04 18:33: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: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1126445 | |||
|
Description
Leonid Natapov
2014-05-22 16:42:50 UTC
Stonith disabled is not officially supported, so moving this to rhos5 to be fixed upstream and back ported as desired. Jirka posted a patch, now merged: https://github.com/redhat-openstack/astapor/pull/236 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 |