QA (public) » openQA Project (public) » openQA Tests (public) » Containers and images

This is a good ticket for a squad rotation candidate. I'm blocking it until further notice.

I manually created and ran a Tumbleweed container in SLE Micro 5.5 and migrated it to SLE Micro 6.0. Afterwards, I validated the container's status. I configured the container to start automatically as a systemd service. After the migration, I ensured that the container was running and validated its status.

• Container creation.

  localhost:~ # podman image ls
  REPOSITORY                                 TAG         IMAGE ID      CREATED       SIZE
  registry.opensuse.org/opensuse/tumbleweed  latest      2f7e3aae2e12  36 hours ago  143 MB
  localhost:~ # podman create --name tumbleweed_container_test registry.opensuse.org/opensuse/tumbleweed sleep infinity 
  099d7f272a4bfd6a2f167bd064034ea5074f712d4cd19d5bf287bbb5a4a5e2de
  localhost:~ # podman ps
  CONTAINER ID  IMAGE                                             COMMAND         CREATED         STATUS        PORTS       NAMES
  099d7f272a4b  registry.opensuse.org/opensuse/tumbleweed:latest  sleep infinity  22 seconds ago  Up 3 seconds              tumbleweed_container_test
  localhost:~ # podman container inspect  --format='{{.State.Running}}' tumbleweed_container_test
  true
  localhost:~ # podman inspect -f '{{.NetworkSettings.IPAddress}}' tumbleweed_container_test 
  10.88.0.2
  

• Configure the container to start automatically as a systemd service.

  localhost:~ # podman generate systemd --new --files --name tumbleweed_container_test 
  /root/container-tumbleweed_container_test.service
  localhost:~ # cp container-tumbleweed_container_test.service  /etc/systemd/system
  localhost:~ # systemctl start container-tumbleweed_container_test.service 
  localhost:~ # systemctl  enable container-tumbleweed_container_test.service 
  Created symlink /etc/systemd/system/default.target.wants/container-tumbleweed_container_test.service → /etc/systemd/system/container-tumbleweed_container_test.service.
  localhost:~ # podman ps 
  CONTAINER ID  IMAGE                                             COMMAND         CREATED        STATUS        PORTS       NAMES
  f5a7a407df10  registry.opensuse.org/opensuse/tumbleweed:latest  sleep infinity  3 minutes ago  Up 3 minutes              tumbleweed_container_test
  localhost:~ # systemctl stop container-tumbleweed_container_test.service 
  localhost:~ # podman ps 
  CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES
  

• Validate the status of the Podman Tumbleweed container after migrating it to SLE Micro 6.0.

  ocalhost login: root
  Password: 
  Last login: Fri Apr  5 09:05:44 UTC 2024 on ttyS0
  Activate the web console with: systemctl enable --now cockpit.socket
  Have a lot of fun...
  localhost:~ # podman ps
  CONTAINER ID  IMAGE                                             COMMAND         CREATED         STATUS         PORTS       NAMES
  81f90c282f2a  registry.opensuse.org/opensuse/tumbleweed:latest  sleep infinity  14 seconds ago  Up 15 seconds              tumbleweed_container_test
  localhost:~ #
  

  Now the next plan is to continue automation with the above steps and later extend the podman container part to pods.

dvenkatachala wrote in #note-5:

Now the next plan is to continue automation with the above steps and later extend the podman container part to pods.

This is great! I think you could attempt to simplify the setup by modifying the systemd unit in such a way, that you don't need anything else. I mean that on a fresh system you only need to deploy a systemd unit to /etc/systemd/system, start the unit and the unit creates and destroys the required containers itself?

I have verified the creation of a single Tumbleweed container in SLE-5.5 Micro and ensured the container is running after migrating from SLE-5.5 Micro to SLE-6.0 Micro.

http://deepthi-openqa.qe.suse.de/tests/6857

I will follow up with Felix for further progress .

The current state looks already very good! We agreed to prepare a first PR by extending the current container test by a network check. This means that the container needs to publish a port and provide a testable service, that we can check. e.g. a webserver where we could fetch a predefined website and verify if the expected site (or identifiable parts of it) is being delivered.

The first PR is about running a Podman Nginx container under systemd and ensuring that the Nginx container is still running after the migration
PR : https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19084

Created two containers within a pod under systemd and ensured that both the containers and the pod are running after migrating from SLEM-5.5 to SLEM-6.0.

PR- https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19163.
scheduled in the OSD development job group - https://openqa.suse.de/tests/14130940

When you see that is stable, let us know so we can add it to our test coverage for review. Where this will be if it is already in GMC, in maintenance?

JERiveraMoya wrote in #note-12:

When you see that is stable, let us know so we can add it to our test coverage for review. Where this will be if it is already in GMC, in maintenance?

Currently this is still a prototype.

I remember the agreement was that for SLEM 5.5 -> 6.0 this is going to be tested manually, no?

Hey @etchubykalo, what is the status of this ticket? Are there any updates in the meantime or are you blocked somehow?

working on some higher priority tickets, but this is still on my list.

I feel this ticket is progressing too slow. @etchubykalo what is the status?

This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.