Project

General

Profile

Actions
Copy link

action #127037

open

coordination #127031: [saga][epic] openQA for SUSE customers

coordination #127028: [epic] openQA on SLE+packagehub

os-autoinst on SLE+packagehub size:M

Added by okurz almost 2 years ago. Updated 1 day ago.

Status:
Feedback
Priority:
Low
Assignee:
ybonatakis
Category:
Feature requests
Target version:
Ready
Start date:
2023-03-31
Due date:
% Done:

0%

Estimated time:
Tags:
qaaas

Description

Acceptance criteria

  • AC1: os-autoinst is continuously built+tested+published on latest SLE+packagehub

Suggestions

Files

LatestTest.log (28.7 KB) LatestTest.log ybonatakis, 2024-03-06 10:57

Related issues 1 (0 open — 1 closed)

Copied to openQA Project (public) - action #127541: Test os-autoinst+openQA against openSUSE:Backports:SLE-X in pull request OBS CI checks size:MResolvedybonatakis2023-03-31

Actions
Actions
Copy link
 #1

Updated by okurz almost 2 years ago

  • Priority changed from Normal to Urgent
Actions
Copy link
 #2

Updated by livdywan almost 2 years ago

  • Description updated (diff)
  • Status changed from New to Blocked
  • Assignee set to livdywan
Actions
Copy link
 #3

Updated by mkittler almost 2 years ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by mkittler almost 2 years ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by okurz almost 2 years 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.

Actions
Copy link
 #6

Updated by tinita almost 2 years 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.

Actions
Copy link
 #7

Updated by okurz almost 2 years ago

  • Status changed from New to Blocked
  • Assignee set to livdywan

Ok, cool that you already discussed it big in a group

Actions
Copy link
 #8

Updated by okurz almost 2 years ago

  • Copied to action #127541: Test os-autoinst+openQA against openSUSE:Backports:SLE-X in pull request OBS CI checks size:M added
Actions
Copy link
 #9

Updated by livdywan almost 2 years ago

This is pending the work on #127034

Actions
Copy link
 #10

Updated by okurz almost 2 years 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.

Actions
Copy link
 #12

Updated by mkittler almost 2 years 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
Actions
Copy link
 #13

Updated by okurz almost 2 years ago

  • Status changed from Workable to Blocked
  • Assignee set to okurz
Actions
Copy link
 #14

Updated by livdywan almost 2 years ago

  • Target version changed from Ready to future

okurz wrote:

#128318

I unfortunately forgot to bring it up last week. The blocker isn't on the backlog so for now I'm also moving this ticket to future.

Actions
Copy link
 #15

Updated by okurz almost 2 years 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

Actions
Copy link
 #16

Updated by okurz over 1 year ago

  • Target version changed from Ready to future
Actions
Copy link
 #17

Updated by okurz about 1 year ago

  • Target version changed from future to Tools - Next

Both #127034 and #127541 resolved, good opportunity to continue here.

Actions
Copy link
 #18

Updated by okurz about 1 year ago

  • Target version changed from Tools - Next to Ready
Actions
Copy link
 #19

Updated by okurz about 1 year ago

  • Priority changed from Normal to Low
Actions
Copy link
 #20

Updated by ybonatakis about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to ybonatakis
Actions
Copy link
 #21

Updated by ybonatakis about 1 year 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
Actions
Copy link
 #22

Updated by okurz about 1 year ago

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
Actions
Copy link
 #23

Updated by ybonatakis about 1 year ago

The logs from openSUSE:Backports:SLE-15-SP5:Update/os-autoinst build. Shows the failing tests

Actions
Copy link
 #24

Updated by ybonatakis about 1 year 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?

Actions
Copy link
 #25

Updated by okurz about 1 year ago

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

Actions
Copy link
 #26

Updated by ybonatakis about 1 year 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

Actions
Copy link
 #27

Updated by ybonatakis about 1 year ago

  • Assignee deleted (ybonatakis)
Actions
Copy link
 #28

Updated by okurz 6 months ago

  • Target version changed from Ready to Tools - Next
Actions
Copy link
 #29

Updated by okurz 6 months ago

  • Status changed from Workable to Rejected
  • Assignee set to okurz

As clarified in a meeting with mkittler, hrommel, jstehlik, hsehic, okurz 2024-09-24 (private minutes in #165683-36) we should use SLFO as a base instead of SLE for a potential SUSE offering hence for now no further follow-up is planned here. Further work is conducted as part of #129313

Actions
Copy link
 #30

Updated by okurz 5 months ago

  • Status changed from Rejected to Workable
  • Assignee deleted (okurz)

#129313 might be more long-term than originally considered. We should follow up here as it might also help us for other goals, e.g. #168439

Actions
Copy link
 #32

Updated by okurz 18 days ago

  • Target version changed from Tools - Next to Ready
Actions
Copy link
 #33

Updated by ybonatakis 11 days ago

  • Status changed from Workable to In Progress
  • Assignee set to ybonatakis
Actions
Copy link
 #34

Updated by okurz 11 days ago

  • Description updated (diff)
Actions
Copy link
 #35

Updated by ybonatakis 9 days ago · Edited

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:

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
Actions
Copy link
 #36

Updated by ybonatakis 8 days ago

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:

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/

Actions
Copy link
 #37

Updated by ybonatakis 8 days ago

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

Actions
Copy link
 #38

Updated by ybonatakis 8 days ago · Edited

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
Actions
Copy link
 #40

Updated by ybonatakis 7 days ago

  • Status changed from In Progress to Feedback

Discussed in the unblocked. Needs inputs from Jan or Marius.
open questions for later once the script is in a ready to run state:

  • where will the trigger for this be?
Actions
Copy link

Also available in: Atom PDF