Project

General

Profile

Actions

action #157000

closed

test showing HTTP 301 error (Moved permanently)

Added by pherranz 4 months ago. Updated 4 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
-
Start date:
2024-03-11
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Observation

openQA test in scenario sle-15-SP2-JeOS-for-kvm-and-xen-Updates-x86_64-jeos-containers-podman@uefi-virtio-vga fails in
podman

Test suite description

After booting, setting up, patching and registering
a system based on an already existing SLES15-SP2 JeOS hard disk
image for the KVM and Xen hypervisors provided in the qcow2 format,
the basic functionality of Podman, and it's extended functionality,
like pulling and running a Docker image from a registry are tested.
Furthermore, the functionality of several base images ("3rd party
images"), which are pulled during the tests, is verified.
In addition, the functionality of running pods and managing network
resources with Podman is tested. Container Network Interfaces (CNI)
and the podman functionality with an enabled firewall, as well as
the creation of Open Container Initiative (OCI) compliant base
images with Buildah are tested additionally.
The test is conducted on an x86_64 VM on a KVM host.
This scenario is defined by
https://gitlab.suse.de/qac/qac-openqa-yaml.

Reproducible

Fails since (at least) Build 20240308-1 (current job)

Expected result

Last good: 20240307-1 (or more recent)

Further details

The test is showing an HTTP 301 error (Moved permanently) when trying to run the command podman container exec basic_test_container curl -sfI https://opensuse.org.
Seems that the URL is wrong...

https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/5f63456ab57fbd170219072de0c3e667b65f113f/tests/containers/container_engine.pm#L93


Related issues 1 (0 open1 closed)

Related to Containers - action #156895: test fails in podman: Can't validate outputResolvedmdati2024-03-08

Actions
Actions

Also available in: Atom PDF