Repository navigation
Add two new distributions: RHIVOS-2.0 and RHIVOS-Core-2.0 [HMS-11293] - #2678
Conversation
|
Not so sure about the names. If anyone has any better ideas, I'm open to suggestions. |
|
https://gitlab.com/redhat/services/products/image-builder/ci/images/-/jobs/16427283493 Saw this failure locally too and thought it was my own issue. It works fine with the curl source. I'm not sure why librepo has issues downloading the packages from the RHIVOS repos. |
Uh that's interesting; perhaps we're missing the necessary access for the RHIVOS repository in librepo but have it in curl? |
|
Maybe? I don't know how that would work, tbh. Maybe the repo is missing some metadata needed by librepo? |
d25e3cd to
22f0554
Compare
22f0554 to
b3d1509
Compare
Add two new disributions, rhivos-2 and rhivos-core-2. Each of these services one image type, a qcow2 guest image for RHIVOS developers.
b3d1509 to
d7d74eb
Compare
achilleas-k
changed the title
Add repository configurations for the new RHIVOS distros. One repository for each architecture. These repositories are released and stable and accessible from inside the Red Hat VPN.
d7d74eb to
386a6ad
Compare
Following up on this: This only happened when I was mixing BaseOS and Appstream alongside the RHIVOS repositories (before I realised RHIVOS repositories are alternatives to RHEL, not complementary). I think the librepo source in osbuild might have issues when a package is available from more than one repository. |
Hm, no, here it is again: https://gitlab.com/redhat/services/products/image-builder/ci/images/-/jobs/17214681775#L792 It was working for me locally though. |
75ca57b to
aa9526e
Compare
|
I just remembered, I'm going to have to exclude these from the boot tests or change the way we add cloud-init. I think I need to change the filesystem of the cloud-init image because the kernel can't mount the iso. |
93ed3e1 to
581cf55
Compare
Done. Cloud-init image is now a raw disk with a fat filesystem. |
| ["cloud-localds", os.fspath(iso_path), user_data.name, meta_data.name], | ||
| cwd=tmpdir, | ||
| ) | ||
| iso = pathlib.Path(tmpdir) / "cloud-init.iso" |
There was a problem hiding this comment.
Since it's no longer an iso is there any reason to keep calling it one?
There was a problem hiding this comment.
Yeah, that's quite stupid indeed. Fixed.
brlane-rht
left a comment
brlane-rht
left a comment
There was a problem hiding this comment.
Looks ok, but calling the cloud-init config image an iso when it's a fat image bugs me slightly :)
c5c3dfd to
aca6466
Compare
|
I disabled boot testing for these images. They work fine locally, but hang in CI. I'll figure it out and enable boot tests for these in a followup. |
When generating dynamic build configurations, we determine if a build requires access to the internal Red Hat network by the image name. RHEL and RHIVOS use repositories from inside the Red Hat network for rpmrpeo and the RHIVOS compose.
The librepo source is having issues with the RHIVOS repositories. Work around it for now in tests.
The RHIVOS images are unable to mount iso9660 filesystems. Create the cloud-init image as a fat filesystem for maximum compatibility and attach it to the VM as a raw disk.
I've successfully tested both x86_64 images locally. The boot test in CI hangs indefinitely however (until the job deadline is hit). I will investigate the problem and add support for boot testing these images in our CI at a later date.
aca6466 to
d667baf
Compare
4 participants
Add two new distributions, RHIVOS-2.0 and RHIVOS-Core-2.0. Each defines one image type, qcow2. These are developer VM images for RHIVOS.
The distros types have been added to the config-list to test with the "empty" configuration.
The original version of this PR had these as two new image types under the RHEL 10 distro. Even though RHIVOS is RHEL-based, it makes more sense to define them as separate distributions because they use completely different repositories. Making them RHEL is also inconvenient, since their configurations are very simple.