QA (public) » openQA Project (public)

But there are a lot of open questions that are the same for both tickets.
We solved some of them in our mob session today, and maybe at some point it makes sense to work on both in parallel. But it doesn't make sense that two people try to find out the answers to those questions independently.

This is pending the work on #127034

So far I went through https://en.opensuse.org/openSUSE:Backports_Package_Submission_Process#Project_Setup_for_Package_Hub_15 and chat with some ppl. I collected those info:

• To get a package to PackageHub, it needs a submission from Factory to Backports
  • Backports == PackageHub
  • it is not happening automatically
• Packages to https://packagehub.suse.com/packages/os-autoinst are added by someone. @Wolfgang Engel told me that he gonna add 15SP6

openSUSE:Backports:SLE-15-SP4 and openSUSE:Backports:SLE-15-SP5 builds are failing. Thats why we added only 15SP6 in the work we did for https://progress.opensuse.org/issues/127541. And based on https://progress.opensuse.org/issues/127541#note-29 they are out of scope, as opposed at the description of the ticket.

Finally we add openSUSE:Backports:SLE-15-SP6:Update working on https://progress.opensuse.org/issues/127541 but I couldnt find the package on that repo. it appears only in openSUSE:Backports:SLE-15-SP6

osc se os-autoinst
No matches found for 'os-autoinst' in projects
####################################################################
matches for 'os-autoinst' in packages:

# Project                                                                # Package
devel:openQA                                                             os-autoinst
devel:openQA:GitHub:os-autoinst:os-autoinst:PR-1978                      os-autoinst
devel:openQA:GitHub:os-autoinst:os-autoinst:PR-2143                      os-autoinst
devel:openQA:GitHub:os-autoinst:os-autoinst:PR-2173                      os-autoinst
devel:openQA:GitHub:os-autoinst:os-autoinst:PR-2274                      os-autoinst
devel:openQA:GitHub:os-autoinst:os-autoinst:PR-2276                      os-autoinst
devel:openQA:GitHub:os-autoinst:os-autoinst:PR-2279                      os-autoinst
devel:openQA:GitHub:os-autoinst:os-autoinst:PR-2457                      os-autoinst
devel:openQA:GitHub:os-autoinst:os-autoinst:PR-2458                      os-autoinst
devel:openQA:GitHub:os-autoinst:os-autoinst:PR-2468                      os-autoinst
devel:openQA:tested                                                      os-autoinst
devel:openSUSE:Factory                                                   os-autoinst
home:StefanBruens:branches:devel:openQA:tested                           os-autoinst
home:dheidler:QA                                                         os-autoinst
home:ohollmann:staging:openssl                                           os-autoinst
home:okurz:container                                                     os-autoinst
home:tinita:branches:devel:openQA:GitHub:perlpunk:os-autoinst:PR-13      os-autoinst
home:tinita:branches:devel:openQA:GitHub:perlpunk:os-autoinst:PR-9       os-autoinst
home:tinita:branches:devel:openQA:GitHubLink:perlpunk:os-autoinst:PR-10  os-autoinst
home:tinita:branches:devel:openQA:GitHubLink:perlpunk:os-autoinst:PR-12  os-autoinst
home:tsaupe:branches:devel:languages:perl                                os-autoinst
home:tsaupe:branches:openSUSE:Factory:openqa-worker                      os-autoinst
home:ybonatakis:branches:devel:openQA:tested                             os-autoinst
home:ybonatakis:branches:openSUSE:Backports:SLE-15-SP4:Update            os-autoinst
home:ybonatakis:branches:openSUSE:Backports:SLE-15-SP6                   os-autoinst
home:ybonatakis:branches:openSUSE:Backports:SLE-15:Update                os-autoinst
openSUSE:ALP:Experimental:Slowroll                                       os-autoinst
openSUSE:ALP:Experimental:Slowroll:Base                                  os-autoinst
openSUSE:Backports:SLE-15                                                os-autoinst
openSUSE:Backports:SLE-15-SP1                                            os-autoinst
openSUSE:Backports:SLE-15-SP2                                            os-autoinst
openSUSE:Backports:SLE-15-SP3                                            os-autoinst
openSUSE:Backports:SLE-15-SP3:Update                                     os-autoinst
openSUSE:Backports:SLE-15-SP4                                            os-autoinst
openSUSE:Backports:SLE-15-SP4:Update                                     os-autoinst
openSUSE:Backports:SLE-15-SP5                                            os-autoinst
openSUSE:Backports:SLE-15-SP6                                            os-autoinst
openSUSE:Factory                                                         os-autoinst
openSUSE:Factory:RISCV                                                   os-autoinst
openSUSE:Leap:15.0                                                       os-autoinst
openSUSE:Leap:15.1                                                       os-autoinst
openSUSE:Leap:15.2                                                       os-autoinst
openSUSE:Leap:42.3                                                       os-autoinst
openSUSE:Slowroll:Base                                                   os-autoinst

You already found out helpful points. As discussed in the unblock two points should be done as next step:

1. Find out how to trigger actions whenever a new version of os-autoinst or openQA or other dependencies reaches Factory. If we can't find that out use a scheduled based trigger, like every 10 days
2. Similar to https://github.com/os-autoinst/scripts/blob/master/os-autoinst-obs-auto-submit on 1. trigger a submission from Factory to Backports unless the latest version is already there

We can use osc api to get the os-autoinst version.

❯ osc api -X GET /build/openSUSE:Factory/standard/x86_64/os-autoinst/_buildinfo | grep versrel
  <versrel>4.6.1709676681.c0c1cf8-1</versrel>

I think this can be used to check if os-autoinst has been updated after the https://github.com/os-autoinst/scripts/blob/master/os-autoinst-obs-auto-submit run and determine whether the version made it to Factory.

wdyt?

sure, try it out. The important part is to have automatic updates conducted though

just collecting random thoughts and notes.

Refresh one's memory on how to publish on PackageHub

In my undestanding and from the comments I received:

• needs to have a bugowner.

  • Oli already took ownership. so its done

• then it needs a manual or automatic?? "osc sr" or "osc mr"

  • as part of the Leap15 any submission will update the backports as well (https://en.opensuse.org/openSUSE:Backports_Package_Submission_Process#Packager_workflow_for_Package_Hub_15)
  • meaning no need to submit it twice.

So far we build os-autoinst against openSUSE:Factory, devel:openQA:Leap:15.6 and openSUSE:Backports:SLE-15-SP6:Update https://github.com/os-autoinst/os-autoinst/blob/master/.obs/workflows.yml

@okurz mentioned that the task is to submit automatically from openSUSE:Factory to Backports
AFAIU devel:openQA:tested is somehow is merged into the openSUSE:Factory.
The documentation refers to Leap and Backports. But no for openSUSE:Factory.
As alternative we could directly submit from devel:openQA:tested also to backports but that means we need to track both kinds of requests in our pipeline and handle individual rejections so I think it's better to submit from Factory to Backports as soon as new packages arrive there

Things i wonder:

• if there is an automation in obs, what the meta has to do with this!
• How the os-autoinst ends in openSUSE:Factory anyway. is it automated I guess somewhere in OBS? there is a buildservice-autocommit but not sure what it does
• As we are not the owners of openSUSE:Factory, how can we create a MR to another project?
• By default, all changes delivered to Leap 15 will be reflected in Package Hub 15 for applicable package. Somehow this is not our case!! (https://en.opensuse.org/openSUSE:Backports_Package_Submission_Process#Packager_workflow_for_Package_Hub_15). Should we submit to Leap instead of openSUSE:Backport

ybonatakis wrote in #note-35:

just collecting random thoughts and notes.

Refresh one's memory on how to publish on PackageHub

In my undestanding and from the comments I received:

• needs to have a bugowner.

  • Oli already took ownership. so its done

• then it needs a manual or automatic?? "osc sr" or "osc mr"

  • as part of the Leap15 any submission will update the backports as well (https://en.opensuse.org/openSUSE:Backports_Package_Submission_Process#Packager_workflow_for_Package_Hub_15)
  • meaning no need to submit it twice.

So far we build os-autoinst against openSUSE:Factory, devel:openQA:Leap:15.6 and openSUSE:Backports:SLE-15-SP6:Update https://github.com/os-autoinst/os-autoinst/blob/master/.obs/workflows.yml

@okurz mentioned that the task is to submit automatically from openSUSE:Factory to Backports
AFAIU devel:openQA:tested is somehow is merged into the openSUSE:Factory.
The documentation refers to Leap and Backports. But no for openSUSE:Factory.
As alternative we could directly submit from devel:openQA:tested also to backports but that means we need to track both kinds of requests in our pipeline and handle individual rejections so I think it's better to submit from Factory to Backports as soon as new packages arrive there

Things i wonder:

• if there is an automation in obs, what the meta has to do with this!
• How the os-autoinst ends in openSUSE:Factory anyway. is it automated I guess somewhere in OBS? there is a buildservice-autocommit but not sure what it does

https://github.com/os-autoinst/scripts/blob/b123cf5e2a399f8c6bfac09ba68c54f17d6538a1/os-autoinst-obs-auto-submit#L204
i am also pointed to http://jenkins.qa.suse.de/

• As we are not the owners of openSUSE:Factory, how can we create a MR to another project?
• By default, all changes delivered to Leap 15 will be reflected in Package Hub 15 for applicable package. Somehow this is not our case!! (https://en.opensuse.org/openSUSE:Backports_Package_Submission_Process#Packager_workflow_for_Package_Hub_15)

Looking in the https://github.com/os-autoinst/scripts/blob/b123cf5e2a399f8c6bfac09ba68c54f17d6538a1/os-autoinst-obs-auto-submit I assume that it is not good idea to extend this. But most of the function look like they can reused. Should I extract them to another file?

In case another script is needed, it could go through the same steps with different src_project and dst_project.
where src_project is the openSUSE:Factory and dst_project is either openSUSE:Leap:15.0 or latest openSUSE:Backports:SLE-15-SPx:Update

I dont know what will be in jenkins side.

I will try the dry_run to see what will happen

Not sure whether the params are correct but this is the output from my first attempt. which might shed some light of where changes might be needed

❯ dry_run=1 src_project=openSUSE:Factory submit_target=openSUSE:Leap:15.0 dst_project=openSUSE:Leap:15.0 ./os-autoinst-obs-auto-submit
retry -e -- osc service wait openSUSE:Factory:testing retry
retry -e -- osc co --server-side-source-service-files openSUSE:Factory:testing/retry
xmlstarlet ed -L -u //param[@name='changesrevision'] -v  openSUSE:Factory:testing/retry/_servicedata
diff: openSUSE:Factory:testing/retry/.osc/_servicedata: No such file or directory
diff: openSUSE:Factory:testing/retry/_servicedata: No such file or directory
retry -e -- osc up openSUSE:Factory:testing/retry
./os-autoinst-obs-auto-submit: line 118: openSUSE:Factory:testing/retry/retry.changes: No such file or directory

I create a separate commit based on the discussion https://suse.slack.com/archives/C02AJ1E568M/p1742819642542479?thread_ts=1742818940.840749&cid=C02AJ1E568M

merged. I wonder how to can verify that it does the right thing. not sure if I have to create a dump MR or just wait?

ybonatakis wrote in #note-48:

https://github.com/os-autoinst/scripts/pull/390

I think this wont work as is. the script has to checkout the submit_target_extra before osc sr

Seems related?

https://openqa.opensuse.org/tests/4992727#step/openqa_bootstrap/12

Please also see the relevant Slack conversation

As discussed, we will us the script to request the SR to PackageHub, instead of apply the submit_target_extra in jenkins.

https://github.com/os-autoinst/scripts/pull/388

Specifically this, adding the openSUSE:Leap:15.6 target

https://github.com/os-autoinst/scripts/pull/391 after https://suse.slack.com/archives/C02BXKBMXNV/p1744631269048249?thread_ts=1744628199.018279&cid=C02BXKBMXNV

livdywan wrote in #note-51:

Seems related?

I dont think so

https://openqa.opensuse.org/tests/4992727#step/openqa_bootstrap/12

Please also see the relevant Slack conversation

As discussed, we will us the script to request the SR to PackageHub, instead of apply the submit_target_extra in jenkins.

https://github.com/os-autoinst/scripts/pull/388

Specifically this, adding the openSUSE:Leap:15.6 target

https://build.opensuse.org/repositories/devel:openQA:tested seems like it needs the openSUSE:Backports:SLE-15-SP6:Update repository but I dont have permissions to edit the project. Maybe @okurz can help?

Please don't add any repos there. This repo is used to test against openSUSE: Factory. Just adapt the script where necessary to also submit to ... Backports regardless of the built repos

okurz wrote in #note-58:

Please don't add any repos there. This repo is used to test against openSUSE: Factory. Just adapt the script where necessary to also submit to ... Backports regardless of the built repos

Sure. just a concern tho. would that submit without testing the build against the Backport repo?

I run the script and I saw some request which I revoked
for example https://build.opensuse.org/request/show/1269420

ybonatakis wrote in #note-59:

Sure. just a concern tho. would that submit without testing the build against the Backport repo?

We already build against the Backports repo in devel:openQA and just adding the repo doesn't magically add testing in openQA. That is why I preferred to submit from openSUSE:Factory to Backports. We still might need to change the approach later on to do that instead of creating direct submit requests.

Related: #180866#note-7

I suggest discussing the open question about how to handle the repo preparation and submit requests as part of this ticket. I asked for clarification of how this is supposed to work before, and I didn't get a clear answer so far:

I don't understand why you removed that. Submissions have been recently created and they look fine so just removing that doesn't sound correct

Because it doesn't work:

Waiting while os-autoinst is in progress
  <summary>unknown repository 'openSUSE_Backports_SLE-15-SP6_Update'</summary>
  <details>404 unknown repository 'openSUSE_Backports_SLE-15-SP6_Update'</details>

That is just some log output and not a proof that "it doesn't work". How was https://build.opensuse.org/requests/1271581 created then? I did not personally create that SR

What I observe is the following:

• Jenkins ends up in a loop reporting that there is no such repo
• Something creates an SR, if that's a bot or a person is not clearly distinguishable
• The SR is pending. Who or what is going to review it?

• Find out where https://packagehub.suse.com/packages/os-autoinst comes from
  • The package hub documentation suggests to develop packages in some project with openSUSE:Backports:SLE-15 repository enabled.
  • There is https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP6/os-autoinst (at time of writing 2025-03-14)
    • Looks like at this point packages are submitted directly from openSUSE:Factory from non-tools-team members, e.g. https://build.opensuse.org/request/show/941302
      • We already submit to Factory via https://build.opensuse.org/package/show/devel:openQA:tested/os-autoinst. So would it make sense to add the Backports repository here (to verify that packages are actually able to build against it)?
      • Maybe submit manually or automatically from Factory to openSUSE:Backports:SLE-15-SP6 from our side?
  • What backport repos are actually relevant? Only the most recent published SP. At time of writing 2025-03-14 SLE-15-SP6

Additionally, have these points from the suggestions been discussed? I don't see this in writing anywhere.

livdywan wrote in #note-64:

I suggest discussing the open question about how to handle the repo preparation and submit requests as part of this ticket.

I don't understand why you removed that. Submissions have been recently created and they look fine so just removing that doesn't sound correct

Because it doesn't work:

Waiting while os-autoinst is in progress
  <summary>unknown repository 'openSUSE_Backports_SLE-15-SP6_Update'</summary>
  <details>404 unknown repository 'openSUSE_Backports_SLE-15-SP6_Update'</details>

That is just some log output and not a proof that "it doesn't work". How was https://build.opensuse.org/requests/1271581 created then? I did not personally create that SR

What I observe is the following:

• Jenkins ends up in a loop reporting that there is no such repo
• Something creates an SR, if that's a bot or a person is not clearly distinguishable
• The SR is pending. Who or what is going to review it?

Meanwhile the SR https://build.opensuse.org/requests/1271581 was accepted so to answer your question: the openSUSE maintenance review team, aka. msmeissn

• Find out where https://packagehub.suse.com/packages/os-autoinst comes from
  • The package hub documentation suggests to develop packages in some project with openSUSE:Backports:SLE-15 repository enabled.
  • There is https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP6/os-autoinst (at time of writing 2025-03-14)

Yes, that one. Meanwhile updated by the above SR

    - Looks like at this point packages are submitted directly from openSUSE:Factory from non-tools-team members, e.g. https://build.opensuse.org/request/show/941302

That's years ago, not relevant

        - We already submit to Factory via https://build.opensuse.org/package/show/devel:openQA:tested/os-autoinst. So would it make sense to add the Backports repository here (to verify that packages are actually able to build against it)?

Maybe

        - Maybe submit manually or automatically from Factory to openSUSE:Backports:SLE-15-SP6 from our side?

That was done, see the above SR

- What backport repos are actually relevant? Only the most recent published SP. At time of writing 2025-03-14 SLE-15-SP6

Correct

Additionally, have these points from the suggestions been discussed? I don't see this in writing anywhere.

Yes, have been discussed. Unfortunately ybonatakis has not reflected back all discussion results here but my above answers should suffice

https://github.com/os-autoinst/scripts/pull/393 merged 🤞

livdywan wrote in #note-68:

https://github.com/os-autoinst/scripts/pull/393 merged 🤞

Apparently a request is getting created successfully now?

Warning: failed to fetch meta data for 'openSUSE:Backports:SLE-15-SP6:Update' package 'openQA-devel-container' (new package?) 
WARNING: As the project is in maintenance, a maintenance incident request is
WARNING: being created (instead of a regular submit request). If this is not your
WARNING: intention please revoke it to avoid unnecessary work for all involved parties.
created request id 1273983

Only I don't see the request on SUSE:SLE-15-SP6:Update... might be nice if we could link the request? In the meantime any pointers on how to find it would be appreciated.

Edit: https://build.opensuse.org/request/show/1273983 not a namespaced URL it turns out

$ osc browse 1273983

--> https://build.opensuse.org/request/show/1273983.

In the meantime any pointers on how to find it would be appreciated.

Answered in Slack https://build.opensuse.org/project/requests/devel:openQA:tested

https://github.com/os-autoinst/scripts/pull/390 discussed in the unblock, and merged

livdywan wrote in #note-74:

https://github.com/os-autoinst/scripts/pull/390 discussed in the unblock, and merged

🙏