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.
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 : /opendev. org/openstack/ openstack- ansible. git
git clone -b stable/rocky https:/
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_constrain ts" infrastructure" fetch a list of requirements.
into the 2nd playbook "setup-
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 sfc==0. 0.0 dashboard= =0.0.0 ==0.0.0 dashboard= =0.0.0 heat==0. 0.0 fwaas_dashboard ==0.0.0 =18.0.0. 0rc1
networking_
designate_
horizon==0.0.0
trove_dashboard
octavia_
keystone==0.0.0
cinder==0.0.0
magnum_ui==0.0.0
setuptools==40.0.0
ceilometer==0.0.0
openstack_
nova_powervm==0.0.0
swift==0.0.0
neutron_
nova_lxd=
nova==0.0.0
neutron==0.0.0