action #158976
closedUpdate Ubuntu Host to 24.04
Added by ph03nix 3 months ago. Updated about 1 month ago.
0%
Description
Update the Ubuntu host from 22.04 to 24.04 after the release of 24.04.
We use a pre-build ubuntu image on OSD as starting point for https://openqa.suse.de/group_overview/377 to create an updated HDD image. So, we need to manually build the 24.04 host image and push it to OSD.
JOSE: I created this page some time ago about how to create the initial HDD https://confluence.suse.com/display/qasle/Ubuntu+host+configuration
Acceptance criteria¶
- Use Ubuntu 24.04 instead of 22.04 for the container tests
- Update the https://openqa.suse.de/group_overview/377 group to use 24.04
Updated by clanig 2 months ago
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.
Updated by ph03nix 2 months ago
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.
Updated by ph03nix about 2 months ago
Hey @clanig, what is the status of this ticket? This was supposed to be a rather simple task, are you blocked somehow?
Updated by clanig about 2 months ago · Edited
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.)
Updated by clanig about 2 months ago
- Status changed from In Progress to Workable
- Assignee deleted (
clanig)
As discussed, may somebody else take it on my vacation. I was not able to get the serial terminals running on my openQA instance.
When I had installed the Docker version from Snap, at least roughly every second attempt the machine did initialize the serial terminals on boot.
With the docker version from the Ubuntu repos though, I never got it to initialize the devices before the getty service timed out, even when I delayed the services etc.
I have to mention though, that the boot process did run horribly slow on my openQA instance.
My idea is that some Systemd service dependencies are not specified and this is usually not noticed, because outside of openQA it boots faster. I wish whoever takes this good luck.
Updated by ph03nix about 1 month ago
- Status changed from Workable to In Progress
- Assignee set to ph03nix
Updated by ph03nix about 1 month ago
Created a new VM disk image and updated https://confluence.suse.com/display/qasle/Ubuntu+host+configuration. Will now test the image.
Updated by ph03nix about 1 month ago
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.
Updated by ph03nix about 1 month ago
- Status changed from In Progress to Feedback
Should be done, waiting for test runs to validate.
And then we need to enable podman as well.
Updated by ph03nix about 1 month ago
- Status changed from Feedback to Resolved
Works as expected: https://openqa.suse.de/tests/14582168#settings