Bug 1920574
Summary: | Error setting up base repository when using kickstart in RHEL 8.3 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jared Hocutt <jhocutt> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED DUPLICATE | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.3 | CC: | jcall, jstodola |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
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: | 2021-01-26 19:18:36 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: |
Description
Jared Hocutt
2021-01-26 16:08:17 UTC
I looked at this briefly with Jared and it seems to me that Anaconda gets confused when the kickstart file comes from a web server, but the RPMs come from the ISO... (In reply to John Call from comment #1) > I looked at this briefly with Jared and it seems to me that Anaconda gets > confused when the kickstart file comes from a web server, but the RPMs come > from the ISO... Though I will note that this exact setup of RPMs being from the ISO and the kickstart coming from the network works as expected with a RHEL 8.2 ISO. Jared, this looks like bug 1914955. Could you please try the workaround in bug 1914955#c2 ? You can also try to remove the following line from your kickstart (but be aware that anaconda may use all your disks in case there are other disks than vda): ignoredisk --only-use=vda Hi Jan, Thank you for pointing me to that BZ. I can confirm that the work around did work for the RHEL 8.3 ISO. Specifically, I set this in my kickstart, where vdb is the device that is my ISO in my virtualized environment where I'm reproducing this issue: ``` # Use CDROM installation media # cdrom harddrive --partition=vdb --dir=/ ``` I did not have change or remote the ignoredisk --use-only=vda, which is nice because it makes me feel safer that I won't accidentally wipe all disks in a machine if I didn't mean to. Thanks so much for the help! Feel free to dup this to the BZ you linked. OK, thanks for confirming that it's the same problem as bug 1914955. I'm closing this one as a duplicate. *** This bug has been marked as a duplicate of bug 1914955 *** |