Bug 1647122
| Summary: | Unable to provision a RHEL 8 virtual machine with an AK attached to the kickstart profile | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Radovan Drazny <rdrazny> | ||||
| Component: | Virtualization | Assignee: | Michael Mráka <mmraka> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Red Hat Satellite QA List <satqe-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 580 | CC: | mmraka, rdrazny, tlestach | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | spacewalk-java-2.5.14-130-sat | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-06-19 18:11:14 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: | |||||||
| Attachments: |
|
||||||
I've been able to reproduce the issue when kisckstart has AppStream checked as a child channel. Part of the issue fixed in cobbler.git by
commit 948410a43722080f094ce77b35aeee6cb13911b7
workaround on Python 2.6 - shlex.split can't parse unicode strings
Updated reproducer: 1. sync BaseOS and AppStream child channel custom channels 2. create an activation key registering a system to BaseOS 3. create a RHEL 8 distro 4. create kickstart profile with AppStream child channel enabled and AppStream Addon disabled 5. assign the AK created in the step 2 to the KS from step 4 5. have a system with the Virtualization and Provisioning entitlements enabled and correctly configured 6. go to the Details page of system from the step 5, tab Virtualization -> Provisioning 7. select the KS profile from the step 3 and schedule a provisioning of a virtual system Fixed in spacewalk git by
commit ffbd3d51cf4031199a1126bc4240c46eba894e99
1647122 - don't modify kickstart child channel list
The issue was cause by modification of child channel list (as an unintentional side effect in check function).
Backported to SATELLITE-5.8 as
commit 0f5d7f9691d744973554a822c5e6bfbdbfd5232a
1647122 - don't modify kickstart child channel list
Verified on spacewalk-java-2.5.14-131.el6sat. I was able to successfully provision and register a RHEL 8 guest using the reproducer from the comment #7. VERIFIED 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, 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/RHBA-2019:1551 |
Created attachment 1502577 [details] Missing installation source during the install Description of problem: When provisioning a new virtual RHEL 8 machine, the automatic installation fails with a Installation source error. Version-Release number of selected component (if applicable): spacewalk-java-2.5.14-128.el6sat.noarch RHEL6 based virtualization host How reproducible: Steps to reproduce: 1. sync BaseOS and AppStream child channel custom channels 2. create an activation key registering a system to BaseOS and AppStream channels 3. create a RHEL 8 distro and a kickstart with AppStream child channel enabled in Kickstart Details -> Operating System tab 4. assign the AK created in the step 2 to the KS from step 3 5. have a system with the Virtualization entitlement enabled and correctly configured 6. go to the Details page of system from the step 5, tab Virtualization -> Provisioning 7. select the KS profile from the step 3 and schedule a provisioning of a virtual system Actual results: Automatic installation fails with Installation source error. See the attached screenshot. Expected results: The installation is successful. Additional info: The installation works for a KS profile withou an AK attached, but if you attach an AK to the profile, and then remove it again, the profile stays in the "failing" mode, and subsequent installations fail as well with the same error. The same scenario with RHEL6 and RHEL7 guests works without any issues.