In mixed OS environments, the libvirt-python wheel does not work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Kevin Carter |
Bug Description
The libvirt-python wheel has to be built with the same binary as will be used on the hosts that load it, otherwise the nova service will fail to start due to a mismatch of features between the library and the binary.
This presents a problem in mixed OS environments where it is not possible to build a wheel for each OS and deploy them selectively. Python's wheel naming doesn't allow for differences between OS's, only CPU architectures.
We have two options as far as I can see:
1. As discussed in https:/
2. We could use the same mechanism we use for Ceph python libs and opt to symlink the python libs provided by the distro package into the venv. See
https:/
Option 1 is complex. Option 2 is simple. I think I prefer option 2, but am open to alternative suggestions.
description: | updated |
Changed in openstack-ansible: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in openstack-ansible: | |
assignee: | nobody → Kevin Carter (kevin-carter) |
status: | Confirmed → In Progress |
Option 2 is great if it works. But I am concerned that building on a repo container with uca/newton xenial libvirt installed, then installing the wheel on Trusty and linking the trusty uca/mitaka libs into the venv will possibly break the wheel.