[standalone] /run/libvirt is needed, although libvirt-daemon isn't installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Cédric Jeanneret |
Bug Description
Dear Stacker,
While doing some work on the standalone deploy with podman, I discovered an issue:
Nova containers want to bind-mount /run/libvirt, but apparently, libvirt-daemon is not installed for standalone deploy.
If the absence of the host /run/libvirt directory doesn't cause any trouble with docker, that's not the same for podman.
So I see two possibilities:
- either add libvirt-daemon as a hard dependency
- or create another host location for the "libvirt" shared directory.
The second possibility is OK if and only if the host libvirt service isn't used. This appears to be the case, since the libvirtd is deactivated at some point.
For now, we don't have this issue with the overcloud deploy, as the libvirt packages are still installed in the overcloud-full image:
https:/
But as I suspect this will change with the full containerization, it might be good to ensure we have a safe way out.
Any thoughts?
Cheers,
C.
Changed in tripleo: | |
assignee: | Cédric Jeanneret (cjeanner) → Emilien Macchi (emilienm) |
assignee: | Emilien Macchi (emilienm) → Cédric Jeanneret (cjeanner) |
Fix proposed to branch: master /review. openstack. org/615956
Review: https:/