Project

General

Profile

action #119086

Create ALP staging job group

Added by ph03nix 4 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
2022-10-19
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

We got a request to create an ALP staging group on o3 and schedule staging test runs in a similar way as we do it with SLE Micro: https://openqa.suse.de/group_overview/329

For starting we probably only need the alp_default test run.

History

#2 Updated by ph03nix 3 months ago

Ok, let's do this. Martin pointed me to https://github.com/os-autoinst/openqa-trigger-from-obs

#3 Updated by ph03nix 3 months ago

I've added the ALP Staging job group on openqa.opensuse.org

#4 Updated by ph03nix 3 months ago

I'm wondering how much sense it makes to have a Staging project in openQA, when there are no images in the ALP Staging project on OBS

#5 Updated by ph03nix 3 months ago

  • Priority changed from High to Normal

#6 Updated by ph03nix 3 months ago

  • Status changed from Workable to In Progress
  • Assignee set to ph03nix

#7 Updated by fcrozat 3 months ago

There is now a first set of images in Staging for ALP:

https://download.opensuse.org/repositories/SUSE:/ALP:/Staging:/B/images/

expect Staging A too soon

#8 Updated by ph03nix 3 months ago

Finally managed to re-draft the PR https://github.com/os-autoinst/openqa-trigger-from-obs/pull/183 that should use Statging:[A-Z] from OBS.

I also updated the Medium type to alp 0.1 Staging-kvm x86_64 and the ALP Staging job template in o3.

#10 Updated by ph03nix 3 months ago

  • % Done changed from 0 to 50

#11 Updated by ph03nix 3 months ago

  • Assignee deleted (ph03nix)
  • Priority changed from Normal to High

I manually triggered the first test runs based on the *.before templates in the openqa-trigger-from-obs repository.

See https://openqa.opensuse.org/tests/overview?version=0.1&groupid=105&build=B.22.1&distri=alp

We have two test runs running, which is nice:

  • alp_default
  • alp_default@UEFI

#12 Updated by ph03nix 3 months ago

Suggestion for fixing the failing ansible tests: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15814

#13 Updated by ph03nix 3 months ago

I'm wondering why there is no new openQA test run for the ALP 22.3 image from Staging A or Staging B. We merged SUSE:ALP:Staging.xml but on openqa.opensuse.org ALP Staging there is only the 22.1 build that I triggered manually.

#14 Updated by ph03nix 3 months ago

Habemus Staging image test runs: https://openqa.opensuse.org/group_overview/105

#15 Updated by ph03nix 3 months ago

Adding ALP Staging to the opensuse-job definitions: https://github.com/os-autoinst/opensuse-jobgroups/pull/221

#16 Updated by fcrozat 3 months ago

those staging image still uses the "hardcoded" repository in the image (which is why there is a test failure). Test should be adapted to use the associated repository at https://download.opensuse.org/repositories/SUSE:/ALP:/Staging:/A/images/repo/ALP-0.1-x86_64-Media1/ instead.

#17 Updated by ph03nix 3 months ago

  • Assignee set to ph03nix

#18 Updated by ph03nix 3 months ago

We're having two issues in those test runs, take e.g. https://openqa.opensuse.org/tests/2877129

cockpit-service fails with https://openqa.opensuse.org/tests/2877129#step/cockpit_service/14

Problem: the to be installed cockpit-machines-270.2-6.3.noarch requires 'virt-install', but this requirement cannot be provided
  not installable providers: virt-install-4.1.0-3.1.noarch[ALP]
                   virt-install-4.1.0-3.2.noarch[ALP-Build]
                   virt-install-4.1.0-3.4.noarch[ALP-Build]
 Solution 1: install python310-base-3.10.8-8.2.x86_64 from vendor obs://build.opensuse.org/SUSE:ALP:Rings
  replacing python310-base-3.10.7-7.1.x86_64 from vendor obs://build.opensuse.org/SUSE:ALP:Staging
 Solution 2: do not install cockpit-machines-270.2-6.3.noarch
 Solution 3: break cockpit-machines-270.2-6.3.noarch by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 

And ansible is also not happy: https://openqa.opensuse.org/tests/2877129#step/ansible/36

transactional-update -n pkg install ansible git-core sudo > /dev/ttyS0; echo trup-$?- | tee -a /dev/ttyS0
ERROR: zypper install on /.snapshots/4/snapshot failed with exit code 4!
Use '--interactive' for manual problem resolution.
Removing snapshot #4...

#19 Updated by ph03nix 3 months ago

fcrozat wrote:

those staging image still uses the "hardcoded" repository in the image (which is why there is a test failure). Test should be adapted to use the associated repository at https://download.opensuse.org/repositories/SUSE:/ALP:/Staging:/A/images/repo/ALP-0.1-x86_64-Media1/ instead.

Yes, this is likely the source for the above stated error messages. Thank you Frederic!

#21 Updated by ph03nix 3 months ago

  • % Done changed from 50 to 80

#22 Updated by ph03nix 3 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

ansible and cockpit are working now as well. Considering this ticket as resolved.

Also available in: Atom PDF