overcloud deploy with podman fails on step4 with systemctl failed error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Unassigned |
Bug Description
In change I43c4291caf3c8e
TASK [Debug output for task: Start containers for step 4] *******
task path: /var/lib/
Tuesday 05 February 2019 11:04:17 +0000 (0:00:21.796) 0:10:08.022 ******
fatal: [reprosubnode-1]: FAILED! => {
"failed_
"outputs.
"Error stopping container: neutron_ovs_agent",
"Error stopping container: neutron_
"Error stopping container: neutron_dhcp",
"systemctl failed",
"Traceback (most recent call last):",
" File \"/usr/
" subprocess.
" File \"/usr/
" raise CalledProcessEr
"Command '['systemctl', 'stop', u'tripleo_
"Removed symlink /etc/systemd/
"Warning: Stopping tripleo_
" tripleo_
"Removed symlink /etc/systemd/
"Removed symlink /etc/systemd/
"Warning: Stopping tripleo_
" tripleo_
"Removed symlink /etc/systemd/
"Removed symlink /etc/systemd/
"Warning: Stopping tripleo_
" tripleo_
"Removed symlink /etc/systemd/
"Job for tripleo_
So the podman stop raises an error and the systemctl stop command return an exit code 1
from the journal logs for the service:
Feb 06 07:25:36 reprosubnode-
Feb 06 07:25:36 reprosubnode-
Looking at podman issues:
https:/
I'm hoping this would go away after we bump podman as podman-
Changed in tripleo: | |
milestone: | none → stein-3 |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: containers |
Tested with podman- 1.0.0-3. git921f98f. el7 which contains the above change and the issue seems resolved now.