Project

General

Profile

Actions

Feature #8157

open

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 over 9 years ago. Updated almost 7 years ago.

Status:
Need more information
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
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 1 (0 open1 closed)

Related to Foreman Remote Execution - Tracker #8121: Remote Execution TrackerDuplicateDavid Caplan10/27/2014

Actions
Actions #1

Updated by David Caplan over 9 years ago

Actions #2

Updated by Dominic Cleal almost 8 years ago

  • Project changed from Foreman to Foreman Remote Execution
Actions #3

Updated by Marek Hulán almost 8 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.

Actions #4

Updated by Marek Hulán almost 8 years ago

  • translation missing: en.field_release set to 136
Actions #5

Updated by Marek Hulán almost 8 years ago

  • translation missing: en.field_release deleted (136)

pardon

Actions #6

Updated by Anonymous almost 7 years ago

David, any news here?

Actions

Also available in: Atom PDF