Bug 1955331
| Summary: | The Boot ISO installer for CentOS Stream doesn't offer any mirrors that are needed to do the installation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Jan Stodola <jstodola> | ||||
| Component: | anaconda | Assignee: | Jiri Konecny <jkonecny> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | CentOS Stream | CC: | carl, jkonecny, mkolman, phillip.szelat, riehecky, tdawson, tgunders, vslavik | ||||
| Target Milestone: | beta | Keywords: | Triaged | ||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | anaconda-34.25.0.25-1.el9 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1946347 | Environment: | |||||
| Last Closed: | 2022-05-17 12:30:42 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: |
|
||||||
|
Description
Jan Stodola
2021-04-29 21:11:50 UTC
This bug is blocked because it can't be tested on CentOS Stream 9. CentOS Stream 9 doesn't have repo files available yet. They are expected to land in August. Jirko, do you have any news about the repo files? Is this bug still blocked? Hi Jan, Unfortunately, not resolved yet. Should be resolved in next few weeks based on my information. CentOS Stream is now figuring out our mirroring solution for c9s. OK, so I'm moving the bug to 9.0 while waiting for the repo files to be available. We now have CentOS Stream 9 repositories in MirrorManager [0] and have added a repos subpackage to centos-stream-release [1]. The build that includes this [2] should be available in the compose in the next few days. [0] https://pagure.io/fedora-infra/ansible/pull-request/775 [1] https://gitlab.com/redhat/centos-stream/rpms/centos-release/-/merge_requests/13 [2] https://kojihub.stream.centos.org/koji/buildinfo?buildID=14386 Hi Carl, I wanted to test my changes but I wasn't able to because the repo files are not installed into the installer environment. The repo files should be in the /etc/anaconda.repos.d/ path, however, nothing is there. The package is not listed in /root/lorax-packages.log. I guess there is some problem with lorax templates not dragging in the dependency of centos-stream-release package properly, not sure why. It should be handled by https://gitlab.com/redhat/centos-stream/rpms/centos-release/-/blob/c9s/centos-stream-release.spec#L16 but it does not work. I tested https://composes.stream.centos.org/development/latest-CentOS-Stream/compose/BaseOS/x86_64/iso/ (CentOS-Stream-9-20211125.d.0-x86_64-boot.iso). Could you please take a look why is this happening? Carl is the correct person for CentOS Stream 8, but I'm doing more for CentOS Stream 9, so I'm looking into this. To answer a few questions. centos-release-repo's has been created. centos-release Requires it, so pulling in centos-release *should* pull in centos-release-repo's. I have verified with todays production compose (entOS-Stream-9-20211201.1), that /etc/anaconda.repos.d/ is populated with centos.repo. Can you please test the latest CentOS Stream 9 production compose (20211201.1 or later) Hi, yes, I tested it and it worked correctly. I used the development ISO which doesn't have these repo files. I wonder why is that happening, is that on purpose? I need to double check, but yes, I believe it is on purpose. The development composes do not go out to the mirrors which brings the question of where do we point the repo's to. The reason the development composes do not go out to the mirrors is that the packages may, or may not have, gone through any testing. If it's a bad package, we don't want it wasting everyone's resources. The development composes are there so a developer who has a new/updated package can see how it affects the whole compose. I'll check into it more and will report back on this bug, but it is my recollection that we don't have the repo's on the devel composes. There are a few reasons that the development compose iso's do not have dnf repos. - We do not put the development composes on the mirrors due to they are not signed. - Because we do not have them on the mirrors, there is the question of where to point the repos. - We would need to implement a different way to get the dnf repo files in place. Create a centos-stream-9-development-repos or create the repo manually in the development kickstart. Could this be setup for the development composes? Yes, but we've been concentrating on getting the production composes fixed. I think if we want to get this done on the development composes also we should have a new bug, or jira ticket. *** Bug 2028937 has been marked as a duplicate of this bug. *** Thank you for explanation Troy, I don't think it should be an issue. Just please make it obvious / visible to people. My point is that they will file bugs on Anaconda because it's not working the expected way. Created attachment 1845525 [details] Closest mirror missing in drop-down menu Jirko, with https://github.com/rhinstaller/anaconda/pull/3478 applied on a CentosStream-9 boot.iso, the installer by default uses the closes mirror as expected, however after entering the "Installation Source" spoke, there is no Closest Mirror option in the drop-down menu. See the attached screenshot. Because of that, it's not possible to leave the spoke unless you define another installation source. Did you see the same behavior during your testing? It might be possible I did not create the updates.img properly for my testing. Thanks a lot for spotting this. The problem is that CentOS Stream don't have Closest Mirrors enabled in the configuration file. PR: https://github.com/rhinstaller/anaconda/pull/3755 Retested with the patch from comment 19 applied. The problem with the Installation Source spoke is fixed and installation from the closest mirror is possible in CentOS Stream. Verified:Tested Checked that anaconda-34.25.0.25-1.el9 is in nightly compose RHEL-9.0.0-20220127.4 There's no documentation needed for this bug - not checking Moving to 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 (new packages: anaconda), 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-2022:2326 |