Trying to build an image for oVirt Node based on CentOS Stream 9. I'm using the code from https://gerrit.ovirt.org/c/ovirt-node-ng-image/+/118412
I triggered a scratch build here: https://cbs.centos.org/koji/taskinfo?taskID=2672832 and it failed on anaconda due to oz generated parameters now being obsolete. Screenshot of the failure:
<img alt="screenshot.png" src="/centos-infra/issue/raw/files/2e6648b5dcf6ce6e16e8caf3378ba4610334969465efa26e5eecd3891caf0f7d-screenshot.png" />
Is there another way to build images for CentOS Stream 9? If not, any suggestion on how to get oz generating a compatible output?
Metadata Update from @zlopez: - Issue tagged with: centos-stream
any update?
Is this ticket related to #708?
in #708 I'm building on centos stream 8. Here I'm building on centos stream 9 and reported error is different
Metadata Update from @zlopez: - Issue assigned to arrfab
@sbonazzo we had a quick look and based on the screenshot it seems it's due to OZ missing the inst.ks (and was using ks=) so it was "hot-patched" (through ansible kojid role that has it now) and I kicked a job (resubmit) : let's see how that will go : https://cbs.centos.org/koji/taskinfo?taskID=2800597
Metadata Update from @arrfab: - Issue tagged with: cbs, medium-gain, medium-trouble
it failed but because your ks seems to contain reference to outside resources, like https://mirrors.centos.org, unreachable on koji hosts, so this time it started the install. I'll let you verify at your side but error reported in this ticket is now gone
Metadata Update from @arrfab: - Issue priority set to: Waiting on Reporter (was: Needs Review)
Is there any internal repo I can use while building in koji?
mirror.stream.centos.org has an internal mirror so using normal path would work (same for mirror.centos.org for centos 8s) . All koji repositories are pointing to these internal mirrors to init buildroots btw ;-)
@sbonazzo tempted to close this ticket at the error in cbs is now gone, what do you think ?
@arrfab ok, closing. I'll open another one if I get stuck.
Metadata Update from @sbonazzo: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.