QA » openQA Project » openQA Tests » Containers

Ticket is blocked until the release of 24.04 (expected 25.04.2024).

depends also on devel:kubic:libcontainers:stable repo, still without 24.04 target

It shouldn't depend on this.
https://kubic.opensuse.org/blog/2022-06-10-kubic-retired/

It appears that podman came from there. I will check this and, in case of dependencies, try to decouple from them.

clanig wrote in #note-8:

It shouldn't depend on this.
https://kubic.opensuse.org/blog/2022-06-10-kubic-retired/

It appears that podman came from there. I will check this and, in case of dependencies, try to decouple from them.

Indeed, I also think this repository shouldn't be there. At least I don't remember that is was necessary.

I have created an image and updated multiple parts of the documentation.

I am verifying it is correctly setup.

The image for 24.04 appears not to reboot after command reboot was sent during the test.
I am investigating this.

It just took really long to proceed and did not show a changed image.

Hey @clanig, what is the status of this ticket? This was supposed to be a rather simple task, are you blocked somehow?

After a reboot, the serial console is not reconnected on the new image.
It only reconnects if service serial-getty@hvc0.service is started by manual interaction.
Delaying the service start had no effect apparently.
C.f. https://stratoscamper.qe.suse.de/tests/84#step/update_host/2

Edit: In addition, the original setup guide suggested to either select Docker to be installed during the system installation or later. However, at least in 24.04 selecting Docker at the system installation installs it as Snap. Installing it through the Ubuntu package management though, installs it as usual package. The confusion that came with it caused a significant additional time, because in the beginning it appeared like Snap had gotten the only way to install Docker on Ubuntu and I just noticed late that they had two ways without making this clear anyhow. (As a result, I already made changes to make it run with that new situation, which turned out to be an alternative situation.)

Created a new VM disk image and updated https://confluence.suse.com/display/qasle/Ubuntu+host+configuration. Will now test the image.

New issue: https://openqa.suse.de/tests/14566150#step/bci_prepare/48

pip3 --quiet install --upgrade pip

error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.12/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

https://gitlab.suse.de/qac/qac-openqa-yaml/-/merge_requests/1688 and https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19499.