search

containers / qm

QM is a containerized environment for running Functional Safety qm (Quality Management) software
https://github.com/containers/qm
GNU General Public License v2.0
22 stars 26 forks source link

e2e: Error: no container with name or ID "qm" found: no such container #222

Closed dougsland closed 1 year ago

dougsland commented 1 year ago

e2e is not working out of the box. Removed all images that I had using podman rmi and still failing. We need to investigate.

[ INFO  ] Preparing QM environment
[ INFO  ] ==============================
[ INFO  ] Creating container node1 [QM mode]
Error: no container with name or ID "qm" found: no such container
Error: no container with name or ID "qm" found: no such container
Error: no container with name or ID "qm" found: no such container
Error: no container with name or ID "qm" found: no such container

[ INFO  ] Creating stub systemd service: container-radio in node1 and moving it to container qm inside node1
[ FAILED ] cannot copy container-radio service to qm container
Terminated
[root@dell730 e2e]# podman ps
CONTAINER ID  IMAGE                     COMMAND               CREATED      STATUS      PORTS       NAMES
81b84b0ec0f5  localhost/control:latest  /usr/lib/systemd/...  2 hours ago  Up 2 hours              control
8a5fe39a5952  localhost/node:latest     /usr/lib/systemd/...  2 hours ago  Up 2 hours              node1
[root@dell730 e2e]# podman exec -it node1 bash
[root@node1 ~]# ls
anaconda-ks.cfg         anaconda-post.log        original-ks.cfg
anaconda-post-nochroot.log  container-radio.service
[root@node1 ~]# podman ps
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES
dougsland commented 1 year ago

On Node1 (container) running setup:

[root@node1 ~]# /usr/share/qm/setup
setup has started...
  * rootfs: /usr/lib/qm/rootfs
  * rwetcfs: /etc/qm
  * rwvarfs: /var/qm
  * install dir: /usr/share/qm

Last metadata expiration check: 2:27:45 ago on Thu Sep 28 02:17:05 2023.
Package selinux-policy-targeted-38.1.23-1.el9.noarch is already installed.
Package podman-101:4.5.2~dev-1.20230706090955027646.v4.5.8.g813f1b53b.el9.x86_64 is already installed.
Package systemd-252-18.el9.x86_64 is already installed.
Package bluechi-agent-0.6.0-0.202309271249.git5cd0b2c.el9.x86_64 is already installed.
Package procps-ng-3.3.17-13.el9.x86_64 is already installed.
Package vim-enhanced-2:8.2.2637-20.el9.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Last metadata expiration check: 2:27:46 ago on Thu Sep 28 02:17:05 2023.
Dependencies resolved.
Nothing to do.
Complete!
Failed to start qm.service: Unit qm.service not found.
rhatdan commented 1 year ago

Mo qm container means that the qm.container/qm.service was not started successfully. This means either quadlet failed to process the qm.container into the qm.service, or systemd is failing to start the qm.service.

dougsland commented 1 year ago

I am trying to understand if this else make sense: https://github.com/containers/qm/blob/a378056b9a63accc87bf4a5c9e04c2f214f4e967/setup#L218

dougsland commented 1 year ago

solved via: https://github.com/containers/qm/pull/230