Bug 1274032 - Revert action does not work in job templates
Revert action does not work in job templates
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Provisioning Templates (Show other bugs)
Unspecified Unspecified
unspecified Severity high (vote)
: Beta
: --
Assigned To: Marek Hulan
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2015-10-21 14:27 EDT by jcallaha
Modified: 2016-07-27 04:58 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-27 04:58:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 3951 None None None 2016-04-22 11:57 EDT

  None (edit)
Description jcallaha 2015-10-21 14:27:44 EDT
Description of problem:
The option to revert to a previous version is shown in the UI, however it makes no change to the contents of a job template.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a job template
2. Make multiple saved revisions to the template to build up history.
3. Use the revert action to roll back the template to a previous history.

Actual results:
No change is made.

Expected results:
The template is reverted back to the desired version.
Comment 2 Bryan Kearney 2016-02-16 10:06:50 EST
Upstream bug component is Provisioning Templates
Comment 4 jcallaha 2016-03-17 10:43:18 EDT
Verified in Satellite 6.2 Beta Snap 4. Revert action now appropriately rolls back to the expected version.
Comment 7 errata-xmlrpc 2016-07-27 04:58:15 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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