action #132125
closedAutomatic submission from devel:openQA:tested into openSUSE:Factory no longer working for os-autoinst size:M
0%
Description
Observation¶
The version of os-autoinst in TW is from 2 months ago, apparently the auto-submit is no longer working. This is problem for derived containers like isotovideo:qemu-x86-os-autoinst-distri-opensuse used in CI tests (see https://github.com/os-autoinst/os-autoinst-distri-opensuse/actions/runs/5406505265/jobs/9830108237?pr=17306). To make it worse, there was no notification about any issue until now.
Acceptance criteria¶
AC1: New versions of os-autoinst are submitted into Factory automatically
AC2: We are notified about problems
Suggestions¶
- Look at the pipeline: http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/lastFailedBuild/console
- DONE Fix the faulty package, in this case devel-container
- Monitor the jenkins builds
- As needed extend https://github.com/os-autoinst/scripts/blob/master/os-autoinst-obs-auto-submit
- Make sure that all relevant jenkins builds are configured to notify us, e.g. send an email to a related mailing list. Just configure as post build action "email notification" and add the corresponding mailing list. Here I suggest o3-admins@suse.de and also consider the other related jobs.
Updated by dheidler over 1 year ago
- Subject changed from Automatic submission from devel:openQA:tested into openSUSE:Factory no longer working for os-autoinst to Automatic submission from devel:openQA:tested into openSUSE:Factory no longer working for os-autoinst size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by pvorel over 1 year ago
- Tags set to CI, openQA
Thanks for an investigation.
Verification: once it's working, isotovideo in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17306 should pass.
Updated by jbaier_cz over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to jbaier_cz
Updated by jbaier_cz over 1 year ago
If I understood the error correctly, our scripting expects _servicedata to parse changesrevision, so I updated the service to use obs_scm service and generate changelog. Now I am waiting for next run to see the results.
For the alerting, one option could be to use the Atom feed with failures which Jenkins provides: http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/rssFailed
Updated by okurz over 1 year ago
jbaier_cz wrote:
For the alerting, one option could be to use the Atom feed with failures which Jenkins provides: http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/rssFailed
Multiple options exist but I would go with choosing a solution that does not need a specific action by every team member. I just don't know which mailing list would be good. o3-admins doesn't sound like a good match as it's not about o3 nor admins. We could also send to the Slack room email address. No, I think a new mailing list for that purpose would be better as this way anyone interested in the topic "openQA package submission" could subscribe. WDYT?
Updated by jbaier_cz over 1 year ago
For now, I created a rule to send failures to our ordinary osd-admins mailing list. I agree that this more related to packaging / OBS stuff. I can live with this solution and I am also OK with a new mailing list related to this kind of notification (for me it would end in the same folder anyway). The main question here is probably if anyone outside our team would be interested to receive error notifications about failed submissions.
Updated by pvorel over 1 year ago
The main question here is probably if anyone outside our team would be interested to receive error notifications about failed submissions.
I'd prefer if it just works. If there are likely longer updates, having it posted in slack channel would work for me (maybe into #eng-testing). Other option would be to add it to the developer option on the status web page https://status.opensuse.org/, there is already openQA.
Updated by okurz over 1 year ago
pvorel wrote:
The main question here is probably if anyone outside our team would be interested to receive error notifications about failed submissions.
I'd prefer if it just works. If there are likely longer updates, having it posted in slack channel would work for me (maybe into #eng-testing). Other option would be to add it to the developer option on the status web page https://status.opensuse.org/, there is already openQA.
status.opensuse.org does not fit though as jenkins.qa.suse.de is not a public facing service. The question is only about that. For now we will use osd-admins@suse.de
Updated by jbaier_cz over 1 year ago
So it turned out, our scripts cannot (yet) handle containers very well. We are expecting the package to have a spec file which is not the case for containers. I will update to script to handle that situation.
Updated by openqa_review over 1 year ago
- Due date set to 2023-07-14
Setting due date based on mean cycle time of SUSE QE Tools
Updated by jbaier_cz over 1 year ago
- Status changed from In Progress to Feedback
The submission script was updated by https://github.com/os-autoinst/scripts/pull/240; we will see in the next run if the os-autoinst will be finally submitted. AC2 (notifications) is already done.
Updated by jbaier_cz over 1 year ago
- Status changed from Feedback to In Progress
Submission (https://build.opensuse.org/request/show/1096496) which should solve the CI issue was created by a manual run with the merged code. I need to find out, why the pipeline run behaves differently then the manual one.
Updated by jbaier_cz over 1 year ago
- Status changed from In Progress to Resolved
Jenkins build is back to normal : submit-openQA-TW-to-oS_Fctry
Finished: SUCCESS
CI issues are solved, the process is fully automatic again. SR needs to be accepted and then the CI issues will be gone as well.