I fail to start osbuild-composer service on Fedora 34 s390x and ppc64le (we'll soon move to Fedora 35, I bet it has the same problem today). The error looks like: Error initializing weldr API: Host distro does not support host architecture: invalid architecture: ppc64le Error initializing weldr API: Host distro does not support host architecture: invalid architecture: s390x Seems expected, as the code for ppc64le and s390x doesn't exist: https://github.com/osbuild/osbuild-composer/blob/a6f40f807dd057dda98b48b2520b55ee29d1908e/internal/distro/fedora33/distro.go#L958 This is the first issue that I noticed that will block us from using composer for generating Fedora Copr images. Currently, we support x86_64, ppc64le, aarch64 and s390x architectures (on x86_64 and aarch64 composer seems to start and cli seems to do something (tested a basic compose).
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
@obudai for your awareness. Not sure how to handle/prioritise this. I assume the first issue is lack of testing / CI. But if that was solved, this would be easy. Pavel, what's the platform you are using libvirt? So you just need qcow2's?
(In reply to Tom Gundersen from comment #2) > @obudai for your awareness. > > Not sure how to handle/prioritise this. I assume the first issue is lack of > testing / CI. We can do manual tests for sure. Or can we help somehow? > But if that was solved, this would be easy. Pavel, what's the > platform you are using libvirt? So you just need qcow2's? - ppc64le, x86_64 libvirt HVs are currently used for generating qcow2 - IBM Cloud VM s390x instances are used for generating qcow2 images - VM snapshot in AWS are used (aarch64 and x86_64) We'd like to unify this complicated set of processes ^^^ into a simple one.
FTR, I've created a tracking epic for this initiative (https://issues.redhat.com/browse/COMPOSER-1706, sorry, RH-internal only). Let's discuss it when we are planning for Q4.
(In reply to Tom Gundersen from comment #2) > I assume the first issue is lack of testing / CI. I don't think this needs to be CI tested actually. As the early adopters, we are fine to use a pre-release, untested feature and tweak the code (and provide patches if something gets broken).
PR by Tomáš comes here: https://github.com/osbuild/images/pull/198