action #127037
opencoordination #127031: [saga][epic] openQA for SUSE customers
coordination #127028: [epic] openQA on SLE+packagehub
os-autoinst on SLE+packagehub size:M
0%
Description
Acceptance criteria¶
- AC1: os-autoinst is continuously built+tested+published on latest SLE+packagehub
Suggestions¶
- Wait for the outcome of #127034 and #127541
- Refresh one's memory on how to publish on PackageHub
- 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-15repository enabled. - Apparently there is https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP4/os-autoinst and https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP5/os-autoinst but it is not clear where those packages are developed at.
- 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-SP4 and openSUSE:Backports:SLE-15-SP5 from our side?
- 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
- What backport repos are actually relevant? Supposedly openSUSE:Backports:SLE-15-SP4 and openSUSE:Backports:SLE-15-SP5.
- We decided to go for SP4 only for now.
- The package hub documentation suggests to develop packages in some project with
Files
Updated by livdywan about 1 year ago
- Description updated (diff)
- Status changed from New to Blocked
- Assignee set to livdywan
Updated by okurz about 1 year ago
- Status changed from Blocked to New
- Assignee deleted (
livdywan)
Due to the urgency I recommend to look into this issue independently from the story about openQA as a whole. This is why I created this separate ticket. os-autoinst is certainly easier than trying to fix the complete openQA worker stack in one go.
Updated by tinita about 1 year ago
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.
Updated by okurz about 1 year ago
- Status changed from New to Blocked
- Assignee set to livdywan
Ok, cool that you already discussed it big in a group
Updated by okurz about 1 year ago
- Copied to action #127541: Test os-autoinst+openQA against openSUSE:Backports:SLE-X in pull request OBS CI checks size:M added
Updated by okurz about 1 year ago
- Status changed from Blocked to New
- Assignee deleted (
livdywan) - Priority changed from Urgent to High
#127034 is resolved showing that the version of openQA currently in SLE+packagehub has no problem to install.
Updated by mkittler about 1 year ago
- Subject changed from os-autoinst on SLE+package to os-autoinst on SLE+package size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by okurz 11 months ago
- Subject changed from os-autoinst on SLE+package size:M to os-autoinst on SLE+packagehub size:M
- Status changed from Blocked to Workable
- Assignee deleted (
okurz) - Priority changed from High to Normal
- Target version changed from future to Ready
We can actually follow up as originally defined with SLE+packagehub
Updated by ybonatakis about 2 months ago
- Status changed from Workable to In Progress
- Assignee set to ybonatakis
Updated by ybonatakis about 2 months ago · Edited
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
Updated by okurz about 2 months ago
You already found out helpful points. As discussed in the unblock two points should be done as next step:
- 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
- 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
Updated by ybonatakis about 2 months ago
- File LatestTest.log LatestTest.log added
The logs from openSUSE:Backports:SLE-15-SP5:Update/os-autoinst build. Shows the failing tests
Updated by ybonatakis about 2 months ago
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?
Updated by okurz about 2 months ago
sure, try it out. The important part is to have automatic updates conducted though
Updated by ybonatakis about 2 months ago
- Status changed from In Progress to Workable
back in workable. I am struggling with obs and i want to take a break from it, and maybe read some stuff before continue. I dont know how to continue without been able to run code against obs