action #175938
closed
[BCI] Skip LTSS tests on non-LTSS hosts
Added by ph03nix 4 months ago.
Updated 3 months ago.
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¶
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¶
- Status changed from Workable to In Progress
- Assignee set to mdati
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.
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.
- Project changed from openQA Tests (public) to Containers and images
- Category deleted (
Bugs in existing tests)
- 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.
Considering the update about the LTSS scope of this ticket, I close the PR#21055.
- 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.
- 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.
- Status changed from Resolved to In Progress
Reopening, as AC1 is not yet resolved.
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.
- Status changed from In Progress to Feedback
The BCI base images LTSS have no more issue present. AC1,2 ok.
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
Also available in: Atom
PDF