Project

General

Profile

Actions
Copy link

action #132125

closed

Automatic submission from devel:openQA:tested into openSUSE:Factory no longer working for os-autoinst size:M

Added by jbaier_cz 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
High
Assignee:
jbaier_cz
Category:
-
Target version:
Ready
Start date:
2023-06-29
Due date:
% Done:

0%

Estimated time:
Tags:
openQA, CI

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

Actions
Copy link
 #1

Updated by dheidler 10 months 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
Actions
Copy link
 #2

Updated by pvorel 10 months 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.

Actions
Copy link
 #3

Updated by jbaier_cz 10 months ago

  • Status changed from Workable to In Progress
  • Assignee set to jbaier_cz
Actions
Copy link
 #4

Updated by jbaier_cz 10 months 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

Actions
Copy link
 #5

Updated by okurz 10 months 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?

Actions
Copy link
 #6

Updated by jbaier_cz 10 months 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.

Actions
Copy link
 #7

Updated by pvorel 10 months 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.

Actions
Copy link
 #8

Updated by okurz 10 months 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

Actions
Copy link
 #9

Updated by jbaier_cz 10 months 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.

Actions
Copy link
 #10

Updated by openqa_review 10 months ago

  • Due date set to 2023-07-14

Setting due date based on mean cycle time of SUSE QE Tools

Actions
Copy link
 #11

Updated by jbaier_cz 10 months 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.

Actions
Copy link
 #12

Updated by jbaier_cz 10 months 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.

Actions
Copy link
 #13

Updated by jbaier_cz 10 months 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.

Actions
Copy link
 #14

Updated by jbaier_cz 10 months ago

  • Due date deleted (2023-07-14)
Actions
Copy link

Also available in: Atom PDF