Project

General

Profile

Feature #8157

As a user I would like to ability to rollback the changes invoked by the execution of a remote command manifest (within reason)

Added by David Caplan almost 5 years ago. Updated over 2 years ago.

Status:
Need more information
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

After the invocation of either single or bulk remote execution action, the operator should have the ability to roll back the change to the previous state.


Related issues

Related to Foreman Remote Execution - Tracker #8121: Remote Execution TrackerDuplicate2014-10-27

History

#1 Updated by David Caplan almost 5 years ago

#2 Updated by Dominic Cleal about 3 years ago

  • Project changed from Foreman to Foreman Remote Execution

#3 Updated by Marek Hulán about 3 years ago

  • Status changed from New to Need more information

We could consider defining rollback steps for a template (probably a different job template) but writing it would probably be very tricky.

David, do you have any real world examples that could illustrate what would be good rollback strategy? The concern I have is that's very hard to define robust rollback script when the original job contains more than a single command, one can't say what exactly failed.

#4 Updated by Marek Hulán about 3 years ago

  • Legacy Backlogs Release (now unused) set to 136

#5 Updated by Marek Hulán about 3 years ago

  • Legacy Backlogs Release (now unused) deleted (136)

pardon

#6 Updated by Michael Moll over 2 years ago

David, any news here?

Also available in: Atom PDF