Description of problem: Running stack update(noop or for scaling out) fails while running podman exec --user=root keystone /usr/bin/bootstrap_host_exec keystone keystone-manage bootstrap --bootstrap-password with stderr: cannot exec into container that is not running: container state improper: "Running container: keystone_bootstrap", "$ podman ps -a --filter label=container_name=keystone --filter label=config_id=tripleo_step3 --format {{.Names}}", "b'keystone\\n'", "$ podman exec --user=root keystone /usr/bin/bootstrap_host_exec keystone keystone-manage bootstrap --bootstrap-password hSWHWHHeD2HgCVqprTITYMZCB", "b'cannot exec into container that is not running: container state improper\\n'", "Error running ['podman', 'exec', '--user=root', 'keystone', '/usr/bin/bootstrap_host_exec', 'keystone', 'keystone-manage', 'bootstrap', '--bootstrap-password', 'hSWHWHHeD2HgCVqprTITYMZCB']. [126]", "stderr: cannot exec into container that is not running: container state improper", "Running container: nova_db_sync", "Skipping existing container: nova_db_sync", "Running container: keystone_cron", "Skipping existing container: keystone_cron" Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-10.6.1-0.20190806190500.bdcffcd.el8ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy overcloud 2. Re-run overcloud deploy Actual results: Fails while running podman exec --user=root keystone /usr/bin/bootstrap_host_exec keystone keystone-manage bootstrap --bootstrap-password Expected results: No failure. Additional info: Attaching jobs artifacts.
I ran multiple stack updates without reproducing the issue reported initially.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:2811