Bug 2245050

Summary:	Configured tags are gone when re-running an Ansible job
Product:	Red Hat Satellite	Reporter:	Stefan Meyer <smeyer>
Component:	Ansible - Configuration Management	Assignee:	Girija Soni <gisoni>
Status:	CLOSED ERRATA	QA Contact:	addubey
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.13.4	CC:	addubey, ahumbe, gisoni, gtalreja, lstejska, pcreech, rlavi
Target Milestone:	6.15.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-foreman_remote_execution-12.0.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-23 17:15:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stefan Meyer 2023-10-19 12:34:59 UTC

Description of problem:
- When re-running a job the advanced field "tags" are not re-added to the new job
- The Include/Exclude option is also reset
- The "advanced fields" options are not visible in the "Preview templates" tab

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

How reproducible:
- Everytime

Steps to Reproduce:
1. Goto Hosts => Job Templates
2. Run the job "Run Command - Ansible Default"
3. Select a host and select any command, example "pwd"
4. In the "advanced fields" add a tag "test" and select "include" as tags_flag
5. Run the job
6. After a successfull run press the "Rerun" button
7. The configured tag "test" is now gone

Actual results:
- Tags are not properly copied when re-running a job

Expected results:
- Options from "advanced fields" should be carried over when re-running a job


Additional info:
- The missing tags may cause problems when re-running jobs on failed hosts.
- A re-run may be triggered by another admin user who was not aware that tags may be required

Comment 1 Brad Buckingham 2023-10-30 11:29:29 UTC

Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 2 Girija Soni 2023-11-29 07:58:52 UTC

Created redmine issue https://projects.theforeman.org/issues/36953 from this bug

Comment 5 Bryan Kearney 2023-12-11 16:02:47 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36953 has been resolved.

Comment 9 errata-xmlrpc 2024-04-23 17:15:22 UTC

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 (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2024:2010