Retirement & provisioning playbook does not duplicate details #1443
Conversation
This file contains 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
|
Checked commit AllenBW@655fbdd with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
himdel
approved these changes
Jun 11, 2018
simaishi
pushed a commit
that referenced
this pull request
Jun 12, 2018
Retirement & provisioning playbook does not duplicate details (cherry picked from commit f1278c3) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1590426
|
Gaprindashvili backport details: |
simaishi
pushed a commit
that referenced
this pull request
Aug 14, 2018
Retirement & provisioning playbook does not duplicate details (cherry picked from commit f1278c3) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1591443
|
Fine backport details: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes https://bugzilla.redhat.com/show_bug.cgi?id=1589334
fixed! (what was broken? when multiple playbooks were present, provision/retirement, playbook details and stdout would mirrior the number of playbooks)
and we need to take this back to fine!
closes https://bugzilla.redhat.com/show_bug.cgi?id=1591426