Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1510646 - [RFE] Provide reversion/back-out ansible playbooks [NEEDINFO]
Summary: [RFE] Provide reversion/back-out ansible playbooks
Keywords:
Status: NEW
Alias: None
Product: Red Hat Insights
Classification: Red Hat
Component: Playbooks
Version: unspecified
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Rob Williams
QA Contact: Jeff Needle
Kevin Blake
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-07 22:06 UTC by Matt Ruzicka
Modified: 2019-04-02 05:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
mruzicka: needinfo? (robwilli)


Attachments (Terms of Use)

Description Matt Ruzicka 2017-11-07 22:06:36 UTC
Wasn't sure which component this would be part of.

2. Who is the customer behind the request?


Account: added in first comment

TAM customer: yes
CSM customer: yes
Strategic: yes

3. What is the nature and description of the request?

Customer is looking for an easy way to undue an ansible playbook if the remediation caused problems. Normally they would manually create a snapshot (if it was a VM), apply patch/run playbook, and then rollback to the snapshot if needed.  Not all systems are VMs, but they'd like this reversion to be part of the tolls provided.

4. Why does the customer need this? (List the business requirements here)

Customer is looking to increase confidence in running playbooks and improve operational efficiency.

5. How would the customer like to achieve this? (List the functional requirements here)

No specific suggestion on implementation. Would seem to be playbook/issue specific - either working with yum, reverting configuration settings, etc.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Run a supplied remediation playbook and revert.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

I did not see an existing RFE, but I could have missed it.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

No specific timelines.

9. Is the sales team involved in this request and do they have any additional input?

Not specifically involved but can be if needed.

10. List any affected packages or components.

Insights, Ansible playbooks, remediation instructions

11. Would the customer be able to assist in testing this functionality if implemented?

Yes.

Comment 2 Matt Ruzicka 2018-02-06 21:57:50 UTC
Hello, I wondering if there was any feedback on this request that I could provide the customer. Thank you.


Note You need to log in before you can comment on or make changes to this bug.