Related to https://pagure.io/fedora-infrastructure/issue/11487

Some questions:

• For the package, can't you simply just follow the normal package flow? make a package, review it, etc... just note that it's a small test package for this purpose, but as long as it's got an ok license and builds it should work, right?

• For the target, what kind of buildroot or the like would it use? Or does that not matter at all? and what destination tag would it have?

• would these test builds be garbage collected?

Some questions:

• For the package, can't you simply just follow the normal package flow? make a package, review it, etc... just note that it's a small test package for this purpose, but as long as it's got an ok license and builds it should work, right?

What I meant here is only a "package" within Koji. Such as e.g. https://koji.fedoraproject.org/koji/packageinfo?packageID=22087 or https://koji.fedoraproject.org/koji/packageinfo?packageID=35893.

The intention is to just have a "dummy" package in Koji for testing image builds.

So no real package in the sense of an RPM is needed. Since there is nothing I could submit for a review or put into dist-git, I didn't consider the Package Review process. Does that make sense?

• For the target, what kind of buildroot or the like would it use? Or does that not matter at all? and what destination tag would it have?

I think that it can be empty, since the "osbuildImage" task takes the repo URLs as its arguments. These repos are then used for the content that goes into the image. Therefore building of images is agnostic to the Koji buildroot (AFAICT).

• would these test builds be garbage collected?

Yes. Keeping the build just for a few days (at maximum a week) should be enough for our use case. Our automation also skips tagging of the build if that's relevant for garbage collection (it was in RH Koji).

Hey @kevin.

I just want to check if you need any additional information from my side or if this is just pending in your TODO (which is completely OK)?

Thanks.

yeah, sorry for the delay here.

Only question left from my side that I am confused by... you want a "osbuild-test" target... but when creating that I need a for it. (Even if osbuild doesn't use that).

What should I specify for those?

yeah, sorry for the delay here.

No worries ;) I'm just trying to keep things moving :sweat_smile:

Only question left from my side that I am confused by... you want a "osbuild-test" target... but when creating that I need a for it. (Even if osbuild doesn't use that).

What should I specify for those?

I checked what we use in RH Brew and there is also "osbuild-test" tag defined. This tag is then used as the build and destination tag for the "osbuild-test" target.

The "osbuild-test" tag contains only a single koji package, the "osbuild-test-image".

Does that help?

Yep. Ok, all done.

Can you check and confirm all works as expected?

Yep. Ok, all done.

Can you check and confirm all works as expected?

Thanks!

I successfully tested the setup in production Koji - https://koji.fedoraproject.org/koji/taskinfo?taskID=106177971

However, the setup in stage Koji for "osbuildImage" task does not seem to be in a good shape, since the task is not getting picked up by any builder - https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=110137653. Nevertheless stage Koji didn't scream at me while using the "osbuild-test-image" package and "osbuild-test" target... Should I create a new ticket for the problem of the task not being picked up by any builder?

We didn't setup any builders in the osbuild channel in stg. ;(

I've done that and it looks like that task was picked up, but then failed due to firewall rules. ;(

So, I fixed that. Can you do another staging one and see if it's all working as expected now?

We didn't setup any builders in the osbuild channel in stg. ;(

Well, it is good that we can now consistently test image builds and catch such issues :wink:

I've done that and it looks like that task was picked up, but then failed due to firewall rules. ;(

Thanks. Yeah, I saw that in the taks...

So, I fixed that. Can you do another staging one and see if it's all working as expected now?

I just triggered https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=110139532 but it seems to be stuck in "free" as well :confused:

stg has a limited number of builders, and it seemed they were all busy. ;(

got it to run, but it failed. not sure why now, it did talk to the api ok.

stg has a limited number of builders, and it seemed they were all busy. ;(

ACK.

got it to run, but it failed. not sure why now, it did talk to the api ok.

Yes, I see it. I think this is a misconfiguration on our workers. Looks like the keytab that we use does not work with staging Koji, or something like that. I'll need to debug this further.

Anyway, I would consider this ticket to be done from the PoV what I requested, so please close it.

Thanks a lot for your help and patience Kevin :blush:

Happy to help out.