contain pcmk_resource within the quickstack pacemaker service#396
Merged
jguiditta merged 1 commit intoredhat-openstack:icehouse_stablefrom Oct 27, 2014
Merged
Conversation
cwolferh
force-pushed
the
pcmk_resource_service_containment
branch
3 times, most recently
from
ebc0860 to
96aa6e7
Compare
https://bugzilla.redhat.com/show_bug.cgi?id=1157340 Make sure dependent pacemaker services are really created within quickstack::pacemaker::resource::service (so that other puppet manifests may make the assumption the pacemaker resource exists after a declaration of quickstack::pacemaker::resource::service).
jguiditta
added a commit
that referenced
this pull request
Oct 27, 2014
contain pcmk_resource within the quickstack pacemaker service
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR it intended to address the error http://fpaste.org/145063/14200364/ discovered by QE . I was not able to reproduce this error in development, despite re-running puppet and deleting pcs resources a couple of dozen times. However, this PR takes a stab at fixing the potential problems:
I tested it, seems to work.