We're seeing this consistently with our periodic tests and getting feedback from our users. Their feedback is that using 'libvirt-python==3.5.0' instead of the Ocata upper-constraint of 'libvirt-python==2.5.0' resolves the issue.
For OSA users the workaround is to use the following override in /etc/openstack_deploy/user_variables.yml:
repo_build_upper_constraints_overrides:
- "libvirt-python==3.5.0"
As a solution, if need be, we may have to add this to global-requirement-pins.txt for Ocata:
libvirt-python==3.5.0
We're seeing this consistently with our periodic tests and getting feedback from our users. Their feedback is that using 'libvirt- python= =3.5.0' instead of the Ocata upper-constraint of 'libvirt- python= =2.5.0' resolves the issue.
For OSA users the workaround is to use the following override in /etc/openstack_ deploy/ user_variables. yml: upper_constrain ts_overrides: python= =3.5.0"
repo_build_
- "libvirt-
As a solution, if need be, we may have to add this to global- requirement- pins.txt for Ocata: python= =3.5.0
libvirt-