Closed Lennonka closed 2 months ago
The PR preview for f5308bb0246067d0b95d7ce07747162f4624c37a is available at theforeman-foreman-documentation-preview-pr-3313.surge.sh
The following output files are affected by this PR:
@evgeni Hi! Can you please review this PR? Should I also remove it from System requirements? Is there anything that needs to be added as well?
I am not exactly an expert in subs (:eyes: @jeremylenz @sideangleside), but will try my best here :)
This is what I know (or think to know, heh):
subscription-manager register
etc) is not affected by this, as that's a RHEL feature, not Katello/Satellitesubscription-manager attach
to obtain specific subs anymore, even if you were using non-SCA mode against the CDN before.For the docs/installation process, this means:
subscription-manager attach …
TL;DR:
Thank you. However, I would prefer additional ack from @jeremylenz. Are we sure about the cherry-picking to older Satellites?
Right, if we're running subscription-manager attach
on the Satellite and not on a host, then it doesn't matter whether the Satellite is SCA-only or not. I agree with @evgeni that this affects all Satellite versions, and we no longer need to attach the Satellite infrastructure subscription anywhere once all RH accounts are SCA.
As to the specific date that RH accounts will all be SCA, we can ask @sideangleside. :eyes:
The date when Red Hat accounts switch to SCA only is on/around 25-Oct-2024, as documented here
Also, subscription-manager
will, in accounts where SCA is enabled, simply 'no-op' the request to attach.
subscription-manager attach --pool "8a85f99c6895cc9901689a87d3f01323"
Ignoring the request to attach. Attaching subscriptions is disabled for organization "XXXXX" because Simple Content Access (SCA) is enabled.
Does it mean I should wait until Oct 25th to merge this PR?
- I am not sure whether this should happen now, or closer to the actual "force-SCA" date
My vote would be to just do it now. thoughts from others welcome
@ehelms Eric, can I merge and cherry pick this now?
@ehelms Eric, can I merge and cherry pick this now?
Do it
- I am not sure whether this should happen now, or closer to the actual "force-SCA" date
My vote would be to just do it now. thoughts from others welcome
So would be mine!
Alrighty then, let's party! :tada:
Cherry-picked:
What changes are you introducing?
Removal of attaching Satellite Infrastructure subscription
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
The procedure is only needed for SCA-disabled organizations, but in Foreman 3.12/Satellite 6.16, all organizations are SCA-enabled and SCA is enforced.
https://issues.redhat.com/browse/SAT-27606
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
I didn't find an include of this module in Installing Server Disconnected. Therefore, no removal there.
Checklists
Please cherry-pick my commits into: