fatal on setup-openstack.yml

[Piotr]

4 servers, openstack xena
while install openstack i have error:
fatal: [compute1_cinder_volumes_container-fbc3c0a9]: FAILED! => {"changed": false, "msg": "You are not building wheels while running role against multiple hosts. This might result in DOS-ing OpenDev infrustructure servers. In order to proceed, please ensure that you have repo servers for selected OS version and architecture. If you want to avoid building wheel on purpose, ensure that you run playbook in serial manner. In case of causing unreasonable load on the opendev.org git servers, your access may be blocked to protect other users and the OpenDev CI infrastructure which are reliant on this service. Found venv_build_targets: {'20.04': {'x86_64': 'controller_repo_container-92be59a1'}}"}
fatal: [compute2_cinder_volumes_container-9501191b]: FAILED! => {"changed": false, "msg": "You are not building wheels while running role against multiple hosts. This might result in DOS-ing OpenDev infrustructure servers. In order to proceed, please ensure that you have repo servers for selected OS version and architecture. If you want to avoid building wheel on purpose, ensure that you run playbook in serial manner. In case of causing unreasonable load on the opendev.org git servers, your access may be blocked to protect other users and the OpenDev CI infrastructure which are reliant on this service. Found venv_build_targets: {'20.04': {'x86_64': 'controller_repo_container-92be59a1'}}"}
fatal: [compute3_cinder_volumes_container-fdb882f6]: FAILED! => {"changed": false, "msg": "You are not building wheels while running role against multiple hosts. This might result in DOS-ing OpenDev infrustructure servers. In order to proceed, please ensure that you have repo servers for selected OS version and architecture. If you want to avoid building wheel on purpose, ensure that you run playbook in serial manner. In case of causing unreasonable load on the opendev.org git servers, your access may be blocked to protect other users and the OpenDev CI infrastructure which are reliant on this service. Found venv_build_targets: {'20.04': {'x86_64': 'controller_repo_container-92be59a1'}}"}

[Piotr (pszmydki)]

everyone has repo container

[Dmitriy Rabotyagov (noonedeadpunk)]

Hi.

That is interesting. Do you have `venv_wheel_build_enable` overwritten anywhere in group variables?

Also does it happen only on cinder-volumes, or you catch that for all services?

[Dmitriy Rabotyagov (noonedeadpunk)]

Also are your cinder-volume containers also running Ubuntu Focal? Or maybe they're still on Bionic (in case you're upgrading)?

[Piotr (pszmydki)]

all is ubuntu focal.
where i can add venv_whell_build_enable and why ansible cannot use container who was created by this same ansible ?

[Dmitriy Rabotyagov (noonedeadpunk)]

Also we don't have that code in Xena - it's present only on master branch. It has been implemented with https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/821415 and was not backported to Xena.

[Piotr (pszmydki)]

and how to configure this ?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/823199

[Dmitriy Rabotyagov (noonedeadpunk)]

We have made pretty silly mistke when introducing this check and error message. Since it's on development branch (not xena) it hasn't been battle tested yet.

I've proposed fix to this. In the meanwhile, you can avoid this message with serial run or using stable/xena instead of current development version.

Also it would be appreciated if you could pull in suggested fix and try it out.

[Piotr (pszmydki)]

no problem.
i add venv_wheel_build_skip_check: true to /etc/openstack_deploy/user_variables.yml

[Dmitriy Rabotyagov (noonedeadpunk)]

I wouldn't recommend having this in production though, as once bug will be fixed and you still have issues with wheel build, that may lead to issues with opendev reachability.

[Piotr (pszmydki)]

ok :-)
this is test and its no problem for me

[Piotr (pszmydki)]

this solution solve tis porblem and i dont see this fatal, but i have other fatal:
TASK [os_neutron : Retrieve the constraints URL]
fatal: [compute3]: FAILED! => {"changed": false, "content": "", "elapsed": 30, "msg": "Status code was -1 and not [200]: Connection failure: timed out", "redirected": false, "status": -1, "url": "http://172.29.236.210:8181/constraints/upper_constraints_e74f91e250d127ff825dad5219527d62efaeb740.txt"}
fatal: [compute2]: FAILED! => {"changed": false, "content": "", "elapsed": 30, "msg": "Status code was -1 and not [200]: Connection failure: timed out", "redirected": false, "status": -1, "url": "http://172.29.236.210:8181/constraints/upper_constraints_e74f91e250d127ff825dad5219527d62efaeb740.txt"}

output from 172.29.236.210:
root@controller:/opt/openstack-ansible/playbooks# netstat -an | grep 8181
tcp 0 0 172.29.236.210:8181 0.0.0.0:* LISTEN
tcp 0 1 172.29.236.210:51568 172.29.237.222:8181 SYN_SENT

i can download this file by wget. i think this task is starting to fast or have to small timeout.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/823199
Committed: https://opendev.org/openstack/ansible-role-python_venv_build/commit/4d826ad133fcd5c6ad924dac565672f5267c33d8
Submitter: "Zuul (22348)"
Branch: master

commit 4d826ad133fcd5c6ad924dac565672f5267c33d8
Author: Dmitriy Rabotyagov <email address hidden>
Date: Thu Dec 30 13:28:01 2021 +0200

    Fix wheel build alert condition

    Currently alert is raised when wheels are built while it should be triggered only
    when they are not.

    Change-Id: I3c3547c3fa6df2bef6834e0cec4d43ef03b82f5f
    Closes-Bug: #1956026