Bug 2014273
| Summary: | opencsd-devel needed to build aarch64 kernel for CentOS Stream 9 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Justin Vreeland <vreeland.justin> |
| Component: | opencsd | Assignee: | Michael Petlan <mpetlan> |
| Status: | CLOSED ERRATA | QA Contact: | Ziqian SUN (Zamir) <zsun> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | acme, bstinson, carl, cye, davide, efuller, jmarchan, jwboyer, mpetlan, ngompa13, skozina, zsun |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | aarch64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-17 13:21:37 UTC | Type: | Enhancement |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Justin Vreeland
2021-10-14 19:19:59 UTC
(In reply to Justin Vreeland from comment #0) > Description of problem: > > The Hyperscale SIG is interested in rebuilding the CentOS Stream 9 kernel. > Currently the c9s kernel package requires opencsd-devel to compile on > aarch64. opencsd-devel appears to be an unshipped package, it can be > produced with the opencsd.spec file available in c9s. We'd like it to be > shipped so we can rebuild the kernel. This is available in the CentOS Stream 9 buildroot. Is there some reason it cannot be used from there? (In reply to Josh Boyer from comment #1) > (In reply to Justin Vreeland from comment #0) > > Description of problem: > > > > The Hyperscale SIG is interested in rebuilding the CentOS Stream 9 kernel. > > Currently the c9s kernel package requires opencsd-devel to compile on > > aarch64. opencsd-devel appears to be an unshipped package, it can be > > produced with the opencsd.spec file available in c9s. We'd like it to be > > shipped so we can rebuild the kernel. > > This is available in the CentOS Stream 9 buildroot. Is there some reason it > cannot be used from there? It can't be used from there because we are only using published repository content. Is there some reason that opencsd-devel can't be shipped? Looking at the upstream project[1], it appears the project is following a semantic versioning model and maintains ABI within a major version since 1.0.0 (which is what both RHEL 8 and RHEL 9 are currently shipping). [1]: https://github.com/Linaro/OpenCSD (In reply to Neal Gompa from comment #2) > (In reply to Josh Boyer from comment #1) > > (In reply to Justin Vreeland from comment #0) > > > Description of problem: > > > > > > The Hyperscale SIG is interested in rebuilding the CentOS Stream 9 kernel. > > > Currently the c9s kernel package requires opencsd-devel to compile on > > > aarch64. opencsd-devel appears to be an unshipped package, it can be > > > produced with the opencsd.spec file available in c9s. We'd like it to be > > > shipped so we can rebuild the kernel. > > > > This is available in the CentOS Stream 9 buildroot. Is there some reason it > > cannot be used from there? > > It can't be used from there because we are only using published repository > content. Is there some reason that opencsd-devel can't be shipped? Looking Why? Is that a SIG specific restriction? From the CBS announcement: "It's also possible to build against CentOS Stream 9 buildroots if the pushed repositories don't include all -devel / runtime packages that you need at buildtime. For that, consider also asking for it if/when needed." > at the upstream project[1], it appears the project is following a semantic > versioning model and maintains ABI within a major version since 1.0.0 (which > is what both RHEL 8 and RHEL 9 are currently shipping). > > [1]: https://github.com/Linaro/OpenCSD Nobody has said this specific -devel package cannot be provided at this time. The team would need to review. However, what is the point of making the entire buildroot available to all SIGs if they do not take advantage of this? At some point this "force it into the product" approach will run into a stalemate because there will be cases where we are not willing to do so. It baffles me that SIGs would block themselves on this.
> This is available in the CentOS Stream 9 buildroot. Is there some reason it
> cannot be used from there?
It does look like our hyperscale-c9s build tags don't include centos9s-buildroot while our 8 tags do, happy to file an infra ticket if that's the right thing.
Even after the tags get updated though, I will end up building kernels for aarch64 if only for testing outside of cbs and noting having to rebuild or reinstall opencsd-devel every time would be very much appreciated.
(In reply to Justin Vreeland from comment #4) > > This is available in the CentOS Stream 9 buildroot. Is there some reason it > > cannot be used from there? > > It does look like our hyperscale-c9s build tags don't include > centos9s-buildroot while our 8 tags do, happy to file an infra ticket if > that's the right thing. > Hmm, I had thought that was intentional. But if we use the buildroot repo for c8s, we should probably just go ahead and enable it for c9s too. 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: opencsd), 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:2496 |