Project

General

Profile

Actions

action #156907

closed

[tools][qe-core][leap15.6 Beta]test fails in openqa_bootstrap with Beta build size:M

Added by rfan1 7 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-03-08
Due date:
% Done:

0%

Estimated time:

Description

Description

/usr/share/openqa/script/openqa-bootstrap command seems add non existing repo with Beta build.

I didn't check the detail script yet, but seems it has something to do with output of uname -r or uname -m command.

I can see below messages in login console:

Welcome to openSUSE Leap 15.6 Beta - Kernel 6.4.0-150600.9-default (hvc0).

https://openqa.opensuse.org/tests/3996597#step/openqa_bootstrap/14 shows that openqa-bootstrap tries to add a repository with content "15.6 Beta" in the URL

So, my questions are:

  1. Does it make sense we test this module in Beta phase?
  2. Can we un-schedule this test in Beta phase? [I can change the test code to skip this test then]

Observation

openQA test in scenario opensuse-15.6-DVD-Updates-x86_64-openqa_bootstrap@64bit fails in
openqa_bootstrap

Test suite description

Maintainer: dheidler. Install openQA using openqa-bootstrap script.

Reproducible

Fails since (at least) Build 20240308-1

Suggestions

Further details

Always latest result in this scenario: latest

Actions #1

Updated by okurz 7 months ago

  • Tags set to reactive work
  • Target version set to Ready
Actions #2

Updated by okurz 7 months ago

  • Category set to Regressions/Crashes
Actions #3

Updated by okurz 7 months ago

  • Subject changed from [tools][qe-core][leap15.6 Beta]test fails in openqa_bootstrap with Beta build. to [tools][qe-core][leap15.6 Beta]test fails in openqa_bootstrap with Beta build size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions #4

Updated by mkittler 7 months ago

  • Status changed from Workable to In Progress
  • Assignee set to mkittler
Actions #5

Updated by mkittler 7 months ago

Actions #6

Updated by mkittler 7 months ago

Not sure how to test this before merging the PR. The test installs the openQA-bootstrap package but this package will never have the version from my PR before merging it.

Actions #7

Updated by okurz 7 months ago

mkittler wrote in #note-6:

Not sure how to test this before merging the PR. The test installs the openQA-bootstrap package but this package will never have the version from my PR before merging it.

You could test that manually, e.g. using the developer mode of the original failing openQA test scenario and then add the corresponding package from devel:openQA:PR:…. Or you could create a temporary change of os-autoinst-distri-opensuse to install the repository corresponding before the original test flow continues. Or you just get the PR merged, wait for the corresponding package change to reach the relevant product (or submit?) and then test in the original scenario.

Actions #8

Updated by mkittler 7 months ago

I went for modifying the test code. I also created a PR with test code changes to make this a proper workaround: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18908

Actions #9

Updated by mkittler 7 months ago

  • Status changed from In Progress to Feedback
Actions #10

Updated by mkittler 7 months ago

I created a SR: https://build.opensuse.org/request/show/1159833

There have not been any relevant dependency changes since the last SR (except for the local-npm-registry but that should be fine) so I hope it'll be fine.

Actions #11

Updated by mkittler 7 months ago

The SR has been merged so let's see whether the test passes on the next build.

Actions #12

Updated by mkittler 7 months ago

The latest job still fails but the package is also still at https://github.com/os-autoinst/openQA/commit/b96c049 despite the SR being accepted.

Actions #14

Updated by okurz 7 months ago

nice!

Actions

Also available in: Atom PDF