Project

General

Profile

Actions

action #154120

closed

coordination #151816: [epic] Handle openQA fixes and job group setup

Handle license agreements when registering modules using suseconnect-ng

Added by zoecao 9 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
2024-01-24
Due date:
% Done:

0%

Estimated time:

Description

Motivation

When registering some modules (like sdk, live patching, ha) by suseconnect-ng, it need additional license agreement. It looks like a new feature of suseconnect-ng, so we need to accept the licences when registering modules by suseconnect-ng.

The related failures in openqa tests:
https://openqa.suse.de/tests/13320365#step/patch_sle/26
https://openqa.suse.de/tests/13320559#step/patch_sle/30

Acceptance criteria

AC1: Accept the licences for the modules

###Additional information
One of a fix for this issue from sap squad: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18483

Actions #1

Updated by JERiveraMoya 8 months ago

  • Tags set to qe-yam-jan-sprint
  • Description updated (diff)
  • Status changed from New to Workable
  • Parent task set to #151816
Actions #2

Updated by syrianidou_sofia 8 months ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia
Actions #3

Updated by leli 8 months ago

The fix already merged, it failed now for do not need activate SLES-LTSS with parameter of '--auto-agree-with-licenses' for SUSEConnect. https://openqa.suse.de/tests/13365946/#step/patch_sle/55

Actions #4

Updated by leli 8 months ago

Actions #5

Updated by JERiveraMoya 8 months ago

it might not be needed when the new version arrives ... https://build.suse.de/request/show/318726#diff_0_n6

Actions #6

Updated by syrianidou_sofia 8 months ago · Edited

The issue doesn't seem to have to do with licensing as the option to auto agree is there:

testapi::assert_script_run(cmd="SUSEConnect -p sle-module-live-patching/\${VERSION_ID}/\${CPU} -r INTERNAL-USE-ONLY-**** --auto-agree-with-licenses", quiet=undef, timeout=300, fail_message="")

But there is a patch_sle failure only for s390x 15SP4 offline tests. Proceeding to further investigation.

Actions #7

Updated by syrianidou_sofia 8 months ago · Edited

The suseconnect-ng package is not updated to the latest one for s390x and the --auto-agree-with-licenses should not be used. We can add a condition to the fix submitted for s390x not to add the parameter, and revert once the s390x package is also updated : https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18555/files

Actions #8

Updated by JERiveraMoya 8 months ago

  • Tags changed from qe-yam-jan-sprint to qe-yam-feb-sprint
Actions #9

Updated by JERiveraMoya 8 months ago

  • Status changed from In Progress to Resolved

merged, let's resolve it and file a ticket for the reminder. thanks.

Actions #10

Updated by openqa_review 8 months ago

  • Status changed from Resolved to Feedback

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: offline_sles15sp4_media_lp-basesys-srv-desk-dev-contm-lgm-wsm-pcm_all_full
https://openqa.suse.de/tests/13458666#step/patch_sle/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #11

Updated by syrianidou_sofia 8 months ago

Probably need to update images: SLES-15-SP4-aarch64-GM-SDK-gnome-allpatterns.qcow2 and SLES-15-SP4-aarch64-GM-gnome.qcow2

Actions #12

Updated by JERiveraMoya 8 months ago

  • Status changed from Feedback to In Progress

we don't use feedback column anymore (the ticket is not visible).

Actions #13

Updated by syrianidou_sofia 8 months ago · Edited

  • Status changed from In Progress to Resolved

JERiveraMoya wrote in #note-12:

we don't use feedback column anymore (the ticket is not visible).

It was set automatically by the osd bot

Actions

Also available in: Atom PDF