On a fresh Ubuntu Xenial host, I tried the following and was unable to replicate the issue:
cd /opt git clone https://github.com/openstack/openstack-ansible cd openstack-ansible git checkout origin/stable/rocky # current SHA: c14e149d04a7a97c36ff4193ff59fdf6318a6d6d ./scripts/bootstrap-ansible.sh ./scripts/bootstrap-aio.sh cd playbooks/ openstack-ansible setup-hosts.yml openstack-ansible lxc-containers-destroy.yml --limit aio1_repo_container-b2f0a852 # answer yes,yes rm -rf /etc/openstack_deploy/ansible_facts openstack-ansible lxc-containers-create.yml --limit lxc_hosts,aio1_repo_container-b2f0a852
It seems that either the issue is resolved or more information is required to replicate the issue.
On a fresh Ubuntu Xenial host, I tried the following and was unable to replicate the issue:
cd /opt /github. com/openstack/ openstack- ansible c36ff4193ff59fd f6318a6d6d bootstrap- ansible. sh bootstrap- aio.sh destroy. yml --limit aio1_repo_ container- b2f0a852 # answer yes,yes deploy/ ansible_ facts create. yml --limit lxc_hosts, aio1_repo_ container- b2f0a852
git clone https:/
cd openstack-ansible
git checkout origin/stable/rocky # current SHA: c14e149d04a7a97
./scripts/
./scripts/
cd playbooks/
openstack-ansible setup-hosts.yml
openstack-ansible lxc-containers-
rm -rf /etc/openstack_
openstack-ansible lxc-containers-
It seems that either the issue is resolved or more information is required to replicate the issue.