[ci] Stein jobs failing due to not having /usr/libexec/paunch-start-podman-container present

Bug #1839073 reported by Jiří Stránský
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Critical
Unassigned

Bug Description

Stein CI is failing e.g. on this backport: https://review.opendev.org/#/c/673799/

Looking at https://logs.opendev.org/99/673799/1/check/tripleo-ci-centos-7-containers-multinode/19d35f9/logs/undercloud/var/log/journal.txt.gz there is:

Aug 05 18:28:56 undercloud.localdomain systemd[1]: Starting neutron_dhcp container...
Aug 05 18:28:56 undercloud.localdomain systemd[1]: Starting rabbitmq healthcheck...
Aug 05 18:28:56 undercloud.localdomain systemd[60807]: Failed at step EXEC spawning /usr/libexec/paunch-start-podman-container: No such file or directory
Aug 05 18:28:56 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service: control process exited, code=exited status=203
Aug 05 18:28:56 undercloud.localdomain systemd[1]: Failed to start neutron_dhcp container.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Unit tripleo_neutron_dhcp.service entered failed state.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service failed.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service holdoff time over, scheduling restart.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Stopped neutron_dhcp container.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Starting neutron_dhcp container...
Aug 05 18:28:57 undercloud.localdomain systemd[60825]: Failed at step EXEC spawning /usr/libexec/paunch-start-podman-container: No such file or directory
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service: control process exited, code=exited status=203
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Failed to start neutron_dhcp container.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Unit tripleo_neutron_dhcp.service entered failed state.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service failed.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service holdoff time over, scheduling restart.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Stopped neutron_dhcp container.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Starting neutron_dhcp container...
Aug 05 18:28:57 undercloud.localdomain systemd[60839]: Failed at step EXEC spawning /usr/libexec/paunch-start-podman-container: No such file or directory
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service: control process exited, code=exited status=203
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Failed to start neutron_dhcp container.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Unit tripleo_neutron_dhcp.service entered failed state.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service failed.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service holdoff time over, scheduling restart.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Stopped neutron_dhcp container.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Starting neutron_dhcp container...
Aug 05 18:28:57 undercloud.localdomain systemd[60977]: Failed at step EXEC spawning /usr/libexec/paunch-start-podman-container: No such file or directory
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service: control process exited, code=exited status=203
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Failed to start neutron_dhcp container.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Unit tripleo_neutron_dhcp.service entered failed state.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service failed.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service holdoff time over, scheduling restart.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Stopped neutron_dhcp container.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Starting neutron_dhcp container...
Aug 05 18:28:57 undercloud.localdomain systemd[60990]: Failed at step EXEC spawning /usr/libexec/paunch-start-podman-container: No such file or directory
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service: control process exited, code=exited status=203
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Failed to start neutron_dhcp container.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: Unit tripleo_neutron_dhcp.service entered failed state.
Aug 05 18:28:57 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service failed.
Aug 05 18:28:58 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service holdoff time over, scheduling restart.
Aug 05 18:28:58 undercloud.localdomain systemd[1]: Stopped neutron_dhcp container.
Aug 05 18:28:58 undercloud.localdomain systemd[1]: start request repeated too quickly for tripleo_neutron_dhcp.service
Aug 05 18:28:58 undercloud.localdomain systemd[1]: Failed to start neutron_dhcp container.
Aug 05 18:28:58 undercloud.localdomain systemd[1]: Unit tripleo_neutron_dhcp.service entered failed state.
Aug 05 18:28:58 undercloud.localdomain systemd[1]: tripleo_neutron_dhcp.service failed.

Looks like this patch may be missing some dependency in stable/stein:

https://github.com/openstack/paunch/commit/b33aeea9728233aca852a3e132f23fca71ac42df

Tags: ci
summary: - Stein jobs failing due to not having /usr/libexec/paunch-start-podman-
- container present
+ [ci] Stein jobs failing due to not having /usr/libexec/paunch-start-
+ podman-container present
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.