action #152963
closed
Remove Leap test runs for LTSS BCI containers
Added by mdati 7 months ago.
Updated 6 months ago.
Description
We should not run the LTSS container test runs on Leap, because we need a LTSS registration which is not available there.
Observation¶
openQA test in scenario sle-15-SP4-BCI-Updates-x86_64-bci-base_15.4-ltss_on_Leap-15.5@64bit fails in
image_podman
- Project changed from openQA Tests to Containers
- Category deleted (
Bugs in existing tests)
- Status changed from New to Workable
Issue present in BCI Base Images ver.15-SP4 and x86_64 only , at any NON-SLES test:
The test fails in https://openqa.suse.de/tests/13140718#step/image_podman/93
running command:
podman run registry.suse.de/suse/sle-15-sp4/update/cr/totest/images/suse/ltss/sle15.4/sle15:15.4 /bin/bash -c 'zypper al udev && zypper -n in systemd'
result:
# wait_serial expected: qr/RkE7X-\d+-/u
# Result:
Specified lock has been successfully added.
Refreshing service 'container-suseconnect-zypp'.
Loading repository data...
Warning: No repositories defined. Operating only with the installed resolvables. Nothing can be installed.
Reading installed packages...
'systemd' not found in package names. Trying capabilities.
No provider of 'systemd' found.
RkE7X-104-
This is expected. SP4 has entered LTSS mode, so the image needs to be registered (by for example passing in registration credentials)
- Subject changed from test fails in image_podman - no zypper repository defined to Remove Leap test runs for LTSS BCI containers
- Description updated (diff)
- Priority changed from Normal to High
- Related to action #152983: BCI repo tests for 15-SP4 and 15-SP3 need LTSS registration code added
- Has duplicate action #152895: test fails in image_podman for LTSS container added
- Status changed from Workable to Resolved
- Assignee set to mgrossu
Also available in: Atom
PDF