action #128318
opencoordination #127031: [saga][epic] openQA for SUSE customers
coordination #127910: [epic] openQA in SLE modules
[spike][timeboxed:20h] Current openQA+os-autoinst+dependencies in pure SLE size:M
0%
Description
Motivation¶
As the parent project about QAaaS progresses we should assess our expected efforts and risks about "openQA in SLE" ASAP for further planning. As according to hsehic openQA needs to be provided from pure SLE, i.e. no PackageHub, we should try what we can achieve in this regard by submitting packages and seeing the effect of that. Maybe some submissions can be directly accepted, maybe some need special treatment. Maybe SLE release managers tell us what processes we need to follow, which bugzilla or Jira tickets we need to create first or which contracts to sign with blood ;)
Goal¶
- G1: All packages for current openQA+os-autoinst+dependencies have non-rejected (open or accepted) submit requests towards SLE
- G2: We know what process we need to follow to get openQA+os-autoinst+dependencies into SLE
Suggestions¶
- Identify all packages not yet in SLE: See the latest pipeline run within https://github.com/os-autoinst/scripts/actions/workflows/obs-list-dependencies.yml
- With a simple for-loop submit all packages from https://build.opensuse.org/project/show/devel:openQA:Leap:15.4 + https://build.opensuse.org/project/show/devel:openQA:tested (or openSUSE:Factory accordingly) to SLE (following https://en.opensuse.org/openSUSE:Maintenance_update_process)
- Make sure the source is openSUSE:Factory to improve chances requests will be accepted (devel:openQA could be seen as a list of relevant packages in that sense)
- React to comments/rejections in SRs accordingly
- List all unattended SRs, i.e. the ones that have open review but apparently after some day receive no update
- If you never worked with build.suse.de okurz suggests to use https://github.com/okurz/scripts/tree/master/isc
- Submit request to https://build.suse.de/package/show/SUSE:SLE-15-SP4:GA/000product to define a new SLE module for openQA
Updated by livdywan about 1 year ago
- Subject changed from [spike][timeboxed:20h] Current openQA+os-autoinst+dependencies in pure SLE to [spike][timeboxed:20h] Current openQA+os-autoinst+dependencies in pure SLE size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by livdywan about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to livdywan
okurz wrote:
- If you never worked with build.suse.de okurz suggests to use https://github.com/okurz/scripts/tree/master/isc
And now the link works :-D
osc -A obs mr openSUSE:Factory git-subrepo openSUSE:Backports:SLE-15-SP4:Update
Using target project 'openSUSE:Maintenance'. (release in 'openSUSE:Backports:SLE-15-SP4:Update')
Default log message was not changed. Press 'c' to continue. openSUSE:Backports:SLE-15-SP3:Update
a)bort, c)ontinue, e)dit: c
108333
This created https://build.opensuse.org/request/show/1083334 - there is no documented suggestion on the log message, so I'm guessing it should be left empty since I'm not making any changes? And presumably my request is mirrored on build.suse.de although I couldn't find it yet.
Updated by openqa_review about 1 year ago
- Due date set to 2023-05-12
Setting due date based on mean cycle time of SUSE QE Tools
Updated by livdywan about 1 year ago
cdywan wrote:
This created https://build.opensuse.org/request/show/1083334 - there is no documented suggestion on the log message, so I'm guessing it should be left empty since I'm not making any changes? And presumably my request is mirrored on build.suse.de although I couldn't find it yet.
I got a first approval so let's assume the workflow is correct.
Found at least one package perl-Compress-Raw-Zlib to be on devel:languages:perl. Unsure if this can be submitted as-is, I guess I'll try and find out.
Not submitting packages from https://build.opensuse.org/project/show/devel:openQA:tested yet since they presumably depend on the previous ones.
Updated by okurz about 1 year ago
cdywan wrote:
cdywan wrote:
This created https://build.opensuse.org/request/show/1083334 - there is no documented suggestion on the log message, so I'm guessing it should be left empty since I'm not making any changes? And presumably my request is mirrored on build.suse.de although I couldn't find it yet.
I got a first approval so let's assume the workflow is correct.
No, most likely not. You submitted to openSUSE:Backports:SLE-15-SP4:Update but there is nothing corresponding to that in SLE so this request will not be mirrored into IBS automatically.
Not submitting packages from https://build.opensuse.org/project/show/devel:openQA:tested yet since they presumably depend on the previous ones.
I guess you could try nevertheless to just "see what happens" :) Could be that we see actual build checks failing due to missing dependencies which would be good but maybe no failures would be visible so then we would know that as well and can plan accordingly.
Updated by livdywan about 1 year ago
- Status changed from In Progress to Feedback
okurz wrote:
No, most likely not. You submitted to openSUSE:Backports:SLE-15-SP4:Update but there is nothing corresponding to that in SLE so this request will not be mirrored into IBS automatically.
As just discussed on Jitsi we'll need to wait for the repo, ideally by Wednesday we'll know how to proceed.
Updated by okurz about 1 year ago
- Due date deleted (
2023-05-12) - Status changed from Feedback to New
- Assignee deleted (
livdywan) - Priority changed from Urgent to Low
- Target version changed from Ready to future
Hi,
Discussed this with Haris yesterday:
Until further notice till a decision was made regarding a SLE extension/module and all it's details we shall not submit new packages into SLE. However I'm preparation as well as to target current Leap+SLE users we should still aim to update existing packages so that known openQA issues in plain Leap and hence in SLE+packagehub are fixed. So expect further update requests in the near future for corresponding packages to their corresponding target projects.
Updated by okurz about 1 year ago
- Copied to action #128651: [spike][timeboxed:20h] Current openQA+os-autoinst+dependencies updated in SLE+packagehub size:M added
Updated by okurz 6 months ago
- Copied to action #154723: Complete list of openQA+os-autoinst+dependencies packages not currently in current SLE in development is known size:M added
Updated by ybonatakis about 2 months ago
- Status changed from Workable to In Progress
- Assignee set to ybonatakis
Updated by openqa_review about 2 months ago
- Due date set to 2024-06-12
Setting due date based on mean cycle time of SUSE QE Tools
Updated by ybonatakis about 1 month ago
- Status changed from In Progress to Workable
I didnt go far as I had problem with my workstation which I was trying to solve since Friday.
Updated by livdywan about 1 month ago
- Due date deleted (
2024-06-12)
So nothing was basically done here. Let's reset the due date then.
Updated by okurz about 1 month ago
- Due date set to 2024-06-19
- Status changed from Workable to In Progress
As SLE15SP6 turned gold it will be readonly. And probably SLE15SP7 has not yet been prepared yet but there must be some external issue that we can block on until SLE15SP7 is ready and then try again.
Updated by ybonatakis about 1 month ago
- Status changed from In Progress to Workable
I asked in two channels about 15SP7. No reply. As I picked up another ticket I change the status to workable
Updated by livdywan about 1 month ago
- Due date deleted (
2024-06-19) - Status changed from Workable to Blocked
- Assignee changed from ybonatakis to livdywan
Updated by okurz about 1 month ago
I suggest to set the ticket to "feedback" and set as due date a sensible date when according to the schedule we can continue. What other ticket would that be "blocked" on?
Updated by livdywan about 1 month ago
- Due date set to 2024-07-31
- Status changed from Blocked to Feedback
okurz wrote in #note-26:
I suggest to set the ticket to "feedback" and set as due date a sensible date when according to the schedule we can continue. What other ticket would that be "blocked" on?
Ack. I tried to find a ticket and drafted the comment in Blocked state.
Updated by okurz about 1 month ago
- Priority changed from High to Low
- Target version changed from Ready to Tools - Next
We need to wait for 15-SP7 to start development. Hence this will take some time until we can update it again with useful content, hence reducing to "Low" and moving to "Next"