action #175938
closed[BCI] Skip LTSS tests on non-LTSS hosts
100%
Description
e.g. sle-15-SP4-BCI-Updates-x86_64-bci-base-fips_15.4_on_ubuntu_docker@64bit fails due to no credentials available on this host.
As discussed in https://confluence.suse.com/display/ENGCTNRSTORY/2025-01-28+-+BCI+Sync we should for now limit the LTSS testing to the LTSS hosts. This means:
- SLES12 LTSS containers should only be tested on a SLES 12 host with LTSS enabled subscription
- SLES15 LTSS containers should only be tested on a SLES 15 host with LTSS enabled subscription
Implementation¶
- First we need to ensure that the SLES12 and SLES15 hosts with available LTSS extensions have those extensions registered and enabled
- We need to find a way to skip LTSS tests in openQA on the hosts, where they are not supposed to run. Probably we need to introduce a new openQA setting for doing so
- This setting needs to be added to LTSS containers in https://gitlab.suse.de/qac/container-release-bot/-/tree/main/containers
- We typically skip BCI tests in https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/ccf5fd29038660999115048b5b2ac04b1d35f34f/tests/containers/bci_test.pm#L28
Acceptance criteria¶
- AC1 : SLES12-LTSS containers are only being tested on a SLES 12 host with LTSS enabled subscription
- AC2 : SLES15-LTSS containers are only being tested on a SLES 15 host with LTSS enabled subscription
More Information¶
Updated by mdati about 2 months ago
- Status changed from Workable to In Progress
- Assignee set to mdati
Updated by mdati about 2 months ago · Edited
I noted that the only FIPS containers seem affected by this credentials missing for non-sle hosts issue, in SLE-15 containers tests.
Moreover, the only 15-SP4/SP3 containers versions show this issue, running on non-sle host, while the upper versions don't.
Tests ongoing, in a dedicated branch, to collect credentials as explained in docs. Initial VR pass; PR coming soon.
Updated by mdati about 1 month ago · Edited
PR created https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21055
Here, as explained into the above bci-guides, for bci tests on non-suse hosts cases, we run a routine performing:
Retrieve SCC credentials from a sle-container and store those on the host in a local file;
perform some validation of the file content;
put that file into the expected SUSE folder.
Then this host is ready to run bci container test.
Updated by ph03nix about 1 month ago
LTSS testing on non-SLES hosts is not supported and likely will also not work, see https://suse.slack.com/archives/C02AF8LALDA/p1737974239183359.
We discuss this topic tomorrow in the BCI meeting, consider it blocked until then. I'll update you after the meeting.
Updated by ph03nix about 1 month ago
- Project changed from openQA Tests (public) to Containers and images
- Category deleted (
Bugs in existing tests)
Updated by ph03nix about 1 month ago
- Subject changed from [BCI] Include SCC credentials on non-SLES hosts to [BCI] Skip LTSS tests on non-LTSS hosts
- Description updated (diff)
I updated the ticket with the new situation. As discussed in todays BCI meeting we need to limit LTSS testing to LTSS hosts and not activate the LTSS subscription.
Updated by mdati about 1 month ago
Considering the update about the LTSS scope of this ticket, I close the PR#21055.
Updated by mdati about 1 month ago · Edited
Prepared 2 merge requests:
MR 2048 https://gitlab.suse.de/qac/qac-openqa-yaml/-/merge_requests/2048 to remove test scenarios of LTSS containers running on hosts either non-sle or without LTSS subscription;
PR 21099 https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21099 to stop BCI tests of LTSS containers on hosts either non-sle or without LTSS subscription.
Updated by mdati about 1 month ago · Edited
- Status changed from In Progress to Feedback
MR 2048 and PR 21099 merged today.
Now SLE LTSS containers are only tested on SLE hosts with LTSS enabled subscription.
Updated by mdati about 1 month ago
- Status changed from Feedback to Resolved
PR #21125, to also display registration status for debug improvement, in BCI_prepare.
The last BCI test results (E.g. in this group) confirm that the introduced LTSS validation works.
Updated by ph03nix about 1 month ago
- Status changed from Resolved to In Progress
Reopening, as AC1 is not yet resolved.
Updated by mdati 29 days ago
PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21160
to update data/containers/autoyast_containers.xml.ep with SLE 12 LTSS. MERGED.
Updated by mdati 29 days ago · Edited
Despite the last update of autoyast to support LTSS registration of 12 SP5 images (see i.e. 16724544), still ltss missing, like https://openqa.suse.de/tests/16725557#step/bci_prepare/45.
The SCC_REGCODE_LTSS codes stored in 12-SP5.*Container-Host product/medium settings are not valid, causing error like: Error: Registration server returned 'the subscription ... does not include product SLE 12 SP5 ...'
New ltss codes needed to create 12-SP5 Container-Host images in t.group 377.
Updated by mdati 23 days ago · Edited
Consider we the note https://progress.opensuse.org/issues/176700#note-5 and related https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21190, because it is needed to use SUSEConnect -l to read extensions and modules available, in place of opt. -s.
Fixed.