I've confirmed that this is still the case in the latest newton tag, 14.2.0.
My guess is that this has something to do with the way the repo_build role builds these wheels. It's not picking up the requirements inside the setup.cfg file.
I think it only picks up requirements inside the global-requirements.txt file in the requirements project, and the requirements.txt file inside each project. A full list of files that are read as part of the py_pkgs lookup can be found here:
We could either convince ceilometer to change their requirements file(which I highly doubt they will do, since the gnocchi client doesn't need to be a requirement for ceilometer deployments not using it), or change our lookup plugin to include setup.cfg as a requirements file type.
Or we could append "gnocchiclient===2.8.2" to repo_build_upper_constraints_overrides whenever gnocchi is deployed.
I've confirmed that this is still the case in the latest newton tag, 14.2.0.
My guess is that this has something to do with the way the repo_build role builds these wheels. It's not picking up the requirements inside the setup.cfg file.
I think it only picks up requirements inside the global- requirements. txt file in the requirements project, and the requirements.txt file inside each project. A full list of files that are read as part of the py_pkgs lookup can be found here:
https:/ /github. com/openstack/ openstack- ansible- plugins/ blob/stable/ newton/ lookup/ py_pkgs. py#L46- L52
We could either convince ceilometer to change their requirements file(which I highly doubt they will do, since the gnocchi client doesn't need to be a requirement for ceilometer deployments not using it), or change our lookup plugin to include setup.cfg as a requirements file type.
Or we could append "gnocchiclient= ==2.8.2" to repo_build_ upper_constrain ts_overrides whenever gnocchi is deployed.