Bug 1625965
| Summary: | RHEL8 provisioning requires more than one enabled repository | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Adam Ruzicka <aruzicka> |
| Component: | Provisioning | Assignee: | Stephen Benjamin <stbenjam> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Hutař <jhutar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | alexander.lackner, bbuckingham, blc, inecas, jan.gerrit, jhutar, jkonecny, jwboyer, ktordeur, mcorr, mkolman, mvanderw, pcreech, rjerrido, sbueno, sshtein, stbenjam |
| Target Milestone: | 6.5.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-14 12:37:51 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: | |||
| Bug Depends On: | 1673032 | ||
| Bug Blocks: | 1670100 | ||
| Attachments: | |||
|
Comment 15
Stephen Benjamin
2018-10-23 13:18:03 UTC
Upstream bug assigned to stbenjam Upstream bug assigned to stbenjam Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25284 has been resolved. *** Bug 1654880 has been marked as a duplicate of this bug. *** Is there a way to test the proposed solution? What are you looking to test? RHEL 8 support is planned for Satellite 6.5. If you are using 6.4 or earlier, and have synced the RHEL 8 content, you might be able to get it to work by manually editing the kickstart template, and adding a `repo` directive pointing at AppStream in addition to BaseOS, and updating any packages (e.g. use chrony instead of ntpd), but it wouldn't be a supported configuration. I am running a Satellite 6.4 and wish to deploy RHEL 6.8 beta. I am aware that both are not supported by Red Hat, that is always the case with Beta pre-releases. Which kickstart template provided by Red Hat has to be edited to be able to do the deployment? 6.8 Beta? Do you mean 8.0? It's called Kickstart default in Satellite 6.4, I believe, you'd have to unlock it or clone it to edit it. RHEL 8.0 beta, sorry for the type error Multiple repo lines in kickstart template causes an installation resource error in anaconda. @Jan: Could you post the template you used? The RHEL7 docs[1] say it should work and when I last tried it it worked. > You can add multiple repo lines. [1] - https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-kickstart-syntax Created attachment 1512443 [details]
The error message while using two repo lines in the kickstart provisioning file
Screen grab of the console showing that the installation source is invalid.
Created attachment 1512446 [details]
The kickstart provisioning file I created by cloning the kickstart default
@Adam: I added the a picture of the installation screen showing the error situation too. Created attachment 1512448 [details]
When trying to fix the installation source issue only one repository is shown
I do not see both repositories, only the BaseOS
My guess would be you need to provide --baseurl=$URL_TO_REPO_IN_SATELLITE to the repo lines. Without it anaconda doesn't know where it should find the "Red Hat Enterprise Linux 8 for x86_64 - AppStream Beta (RPMs)" repository. But take this with a grain of salt, I don't have a machine at hand to test it @Adam: I will test it. @Adam: It did not fix the issue. Even though I specified the baseurl as https URLs, anaconda shows the baseos as a http URL and fails to continue. Will stick to an ISO installation from libvirtd for now. 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/RHSA-2019:1222 |