WIP: include oca in rhel9, 10 image definitions#2463
Conversation
|
You'll need to regenerate checksums by running We use that to ensure each commit only changes expected manifests (and the checksums are also used for caching in our CI so we know if we've already built and boot tested a given image) 🙂 Also tagging in @achilleas-k because he's been working with the virt people on the OCI images if I recall correctly. |
supakeen
left a comment
There was a problem hiding this comment.
Some adjustments to make things work.
Is oracle-cloud-agent shipped in RHEL/CentOS/Alma/Rocky/OL repositories? They all build from the RHEL definitions. If it's not available then all the changes still apply but it'd probably be easier to have a conditions on the qcow2 package sets that includes this only for those distributions that ship the package (and then work on shipping the package elsewhere).
00afbc8 to
7a81a42
Compare
In the case of the cloud-agent, it would be better to have the package in all the images by default, so not in the pungi configs.
There was a problem hiding this comment.
Ok, so it seems the main concern here is that oracle-cloud-agent is not available in RHEL Base/AppStream repositories. Have you already engaged with people to get that in the repositories?
Without it we can't merge this PR as it breaks builds during depsolving for RHEL for any image type that inherits from the qcow2.
For now I think we can either:
- Include it only for distros where it's available. This seems to be only Oracle Linux at the moment.
- Put a hold on this PR until the package is potentially available in RHEL (and maybe CentOS Stream, Alma Linux, Rocky Linux (and potentially Fedora?)).
We've been talking with Simran (and Lars) about the details of the image and the agent already. I told him the agent should be part of the base image since we want it in all OCI images, not just marketplace ones. But I didn't realise (or more like, I was absent minded and didn't make the connection) that the repository wouldn't be available outside of brew builds. So it seems we can't have it as part of the base image unless it gets distributed in Red Hat repos, which I don't think it will be. |
In the case of the cloud-agent, it would be better to have the package in all the images by default