-
Sub-task
-
Resolution: Done
-
Blocker
-
None
-
None
-
0
-
False
-
-
False
-
0
-
Phoenix - Content
-
-
-
Sprint 135, Sprint 136, Sprint 137, Sprint 138, Sprint 139, Sprint 140, Sprint 141
Description of problem:
The provisioning is failing for with `Medium can't be blank` just as the anaconda installer starts for EL9, and For EL8 in the post install process when the subscription manager starts the host registers but content is not added to the host and we see the same error there as well.
How reproducible:
Always
Is this issue a regression from an earlier version:
Regression, was working before snap 60
Steps to Reproduce:
1. Configure a satellite for provisioning
2. Provision a RHEL 9 or RHEL 8
Actual behavior:
For RHEL9: As the anaconda installer starts it halts on a error ->
`Error detail : Medium can't be blank`
For RHEL8 : In the post install while registering the host the same error is seem -> `Error detail : Medium can't be blank`
Expected behavior:
Provisioning should successfully pass on both RHEL8 and RHEL9
Business Impact / Additional info:
DEV Tracker for https://issues.redhat.com/browse/SAT-25789