Feature #36301
closed
Switching on SCA should not give hosts access to new custom repositories
Added by Jeremy Lenz over 1 year ago.
Updated over 1 year ago.
Description
Add a rake task to freeze repo enablement before turning on SCA.
Essentially this is the same as the "Non-SCA" portion of the migration in https://projects.theforeman.org/issues/36120, but you could run it at any time. It would be used before toggling SCA so that the repo enablement state of your custom products wouldn't change on existing hosts and activation keys.
- Related to Tracker #36179: [RFE] Improve custom products workflow when using SCA added
- Status changed from New to Ready For Testing
- Assignee set to Jeremy Lenz
- Pull request https://github.com/Katello/katello/pull/10515 added
- Target version changed from Katello 4.9.0 to Katello 4.8.1
Shall we triage this back to a new 4.7 ? That way we'll get more use out of the script.
- Target version changed from Katello 4.8.1 to Katello 4.7.5
- Triaged changed from No to Yes
- Bugzilla link set to 2188380
- Pull request https://github.com/Katello/katello/pull/10528 added
- Pull request https://github.com/Katello/katello/pull/10529 added
- Status changed from Ready For Testing to Closed
- Target version changed from Katello 4.7.5 to Katello 4.8.1
- Found in Releases Katello 4.9.0 added
- Fixed in Releases Katello 4.9.0 added
- Target version changed from Katello 4.8.1 to Katello 4.7.5
- Fixed in Releases Katello 4.8.1, Katello 4.7.5 added
- Subject changed from Add rake task to prepare for switching orgs to SCA to Switching on SCA should not give hosts access to new custom repositories
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by