Bug 1874153 - Default job templates are not locked
Summary: Default job templates are not locked
Keywords:
Status: CLOSED DUPLICATE of bug 1830253
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.7.0
Hardware: x86_64
OS: Linux
high
unspecified
Target Milestone: 6.8.0
Assignee: Leos Stejskal
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-31 16:15 UTC by James Jeffers
Modified: 2024-03-25 16:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1862260
Environment:
Last Closed: 2020-09-09 11:03:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
6.8-oscap (102.92 KB, image/png)
2020-09-04 11:36 UTC, Peter Ondrejka
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 29901 0 High Closed Default job templates are not locked 2020-10-27 16:28:53 UTC
Foreman Issue Tracker 29956 0 Normal Closed Lock default Job templates 2020-10-27 16:28:52 UTC

Comment 3 Peter Ondrejka 2020-09-04 11:36:06 UTC
Created attachment 1713768 [details]
6.8-oscap

Comment 4 Peter Ondrejka 2020-09-04 11:38:36 UTC
There seems to be one remaining unlocked default template: Run OpenSCAP scans, see attachment

Comment 5 Bryan Kearney 2020-09-04 12:06:04 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/29956 has been resolved.

Comment 6 James Jeffers 2020-09-09 11:03:50 UTC
Peter,

You are correct this BZ is a duplicate. I see what has happened: we originally cloned this for 6.7.3, but was postponed to for 6.7.4. However, I created a clone since it required verification in both streams when that was unecessary (we already had the original in 6.8). The cloning process is new so I am still learning many caveats - apologies for the confusion.

I am closing this as a duplicate.

James

*** This bug has been marked as a duplicate of bug 1830253 ***


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