Undercloud upgrade cannot be re-run after initial failure.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Sofer Athlan-Guyot |
Bug Description
Hi,
Originally reported there https:/
After an failed undercloud upgrade, if says, the ironic-api has been disabled but the container is still not installed then we have a systematic error preventing the upgrade to be run again.
...
fatal: [undercloud-0]: FAILED! => {"changed": true, "cmd": ["docker", "exec", "ironic_api", "ironic-dbsync", "--config-file", "/etc/ironic/
:00:00.036968", "end": "2018-11-20 11:06:53.414249", "msg": "non-zero return code", "rc": 1, "start": "2018-11-20 11:06:53.377281", "stderr": "Error response from daemon: No such container: i
ronic_api", "stderr_lines": ["Error response from daemon: No such container: ironic_api"], "stdout": "", "stdout_lines": []}
tags: |
added: upgrade removed: upgr |
tags: | added: rocky-backport-potential |
Fix proposed to branch: master /review. openstack. org/619247
Review: https:/