#6659 Required infrastructrures changes to run Atomic, Cloud and Docker composes on koji builders for Fedora 28, s390x
Closed 2 years ago Opened 2 years ago by sinnykumari.

I am working on enabling Atomic, Cloud and Docker composes on s390x in Fedora 28. This might require necessary changes in s390x builders to run these additional composes.

Among required packages to run imagefactory for building images, s390x support landed recently in upstream oz master branch which is not yet available in Fedora rawhide. Rest of required package dependencies looks ok.
I have emailed and also filed a bug to include s390x related changes https://bugzilla.redhat.com/show_bug.cgi?id=1535043 in rawhide. I will update this ticket once oz with s390x support is available in Fedora rawhide.

So, what changes are required in infrastructure side for running these composes on s390x builders?

Note: Pungi config related changes can be tracked in PR - https://pagure.io/pungi-fedora/pull-request/496


I cannot think of anything off hand, other than making sure the same packages were installed as are for other arch builders.

We have a few conditionals to not install oz/imagefactory on builders (look in the koji_builder role in ansible). Those will need changed as soon as oz/imagefactory that works on s390x is avaiilable for f27.

Feel fee to let us know when things reach that point...

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

I cannot think of anything off hand, other than making sure the same packages were installed as are for other arch builders.
We have a few conditionals to not install oz/imagefactory on builders (look in the koji_builder role in ansible). Those will need changed as soon as oz/imagefactory that works on s390x is avaiilable for f27.

Thanks @kevin ! good to know

Feel fee to let us know when things reach that point...

Sure. I am waiting for oz PR to get merged

Metadata Update from @sinnykumari:
- Issue status updated to: Open (was: Closed)

2 years ago

Metadata Update from @sinnykumari:
- Issue status updated to: Closed (was: Open)

2 years ago

s390x support in oz is available now with Fedora rawhide update oz-0.16.0-3 . @kevin , will it be possible to update s390x builders with required dependencies to run imagefactory ?

I am not sure what Fedora version s390x builders uses. If they don't use rawhide then we may need to tag oz to required Fedora release.

s390x support in oz is available now with Fedora rawhide update oz-0.16.0-3 . @kevin , will it be possible to update s390x builders with required dependencies to run imagefactory ?

It should be.

I am not sure what Fedora version s390x builders uses. If they don't use rawhide then we may need to tag oz to required Fedora release.

They are using Fedora 27. So, we will need builds for that either in fedora updates (preferred) or our f27-infra koji tag.

They are using Fedora 27. So, we will need builds for that either in fedora updates (preferred) or our f27-infra koji tag.

We have oz-0.16.0-2.fc27 ( with s390x support) in Fedora 27 bodhi update testing now! I will update here once this update is pushed to stable.

@kevin oz-0.16.0-2.fc27 update has been pushed to stable and should be available in F27 now. We can now update s390x koji builders with imagefactory dependencies.

Metadata Update from @sinnykumari:
- Issue status updated to: Open (was: Closed)

2 years ago

ok, in ansible commit 11e384a8c3444edd3e32b407e9b3cf05cb454223 I removed the restrictions in the playbooks that excluded s390x builders from getting oz/imagefactory packages, and ran the playbook.

Now, we need to make sure there's some s390x builders in the right channels to process the images and then modify pungi-fedora config to request them in composes. Those I think are releng things, so we could file a new ticket there and close this, or keep this open until everything is working.

ok, in ansible commit 11e384a8c3444edd3e32b407e9b3cf05cb454223 I removed the restrictions in the playbooks that excluded s390x builders from getting oz/imagefactory packages, and ran the playbook.

Thanks a lot!

Now, we need to make sure there's some s390x builders in the right channels to process the

Opened releng ticket - https://pagure.io/releng/issue/7351

Metadata Update from @sinnykumari:
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata