Comment 3 for bug 1915128

Revision history for this message
Daniel Pham (shin-ichi) wrote :

Hello again,

Thank you for your replies, I used the patch for the LXC image version instead of override this variable.

I used the stable/rocky branch of openstack-ansible to configure my inventory of machines :
git clone -b stable/rocky https://opendev.org/openstack/openstack-ansible.git
Did I have to use the tag rocky-em instead of the stable branch ?

I'm not sure to understand "re-defining openstack_release".
I override the variable into my user_variables.yml file with your version number, but if it did not work :
 Where can I find the list of openstack_release version number ?

During my research I found out that the job "Backup the default pip_install_upper_constraints"
into the 2nd playbook "setup-infrastructure" fetch a list of requirements.

This list seems wrong :

root@os-infra:~# curl http://<internal_lb_vip_address>:8181/os-releases/18.1.21.dev5/ubuntu-18.04-x86_64/requirements_absolute_requirements.txt | grep 0.0.0
networking_sfc==0.0.0
designate_dashboard==0.0.0
horizon==0.0.0
trove_dashboard==0.0.0
octavia_dashboard==0.0.0
keystone==0.0.0
cinder==0.0.0
magnum_ui==0.0.0
setuptools==40.0.0
ceilometer==0.0.0
openstack_heat==0.0.0
nova_powervm==0.0.0
swift==0.0.0
neutron_fwaas_dashboard==0.0.0
nova_lxd==18.0.0.0rc1
nova==0.0.0
neutron==0.0.0