Hi store team,
We’ve added a new `system-files` plug to the `snap-openstack-hypervisor` snap (published by Canonical) as part of adding s390x support. The revision is flagged for manual review because of it.
Plug definition:
plugs:
mdevctl-config:
interface: system-files
read:
- /etc/mdevctl.d
This is connected to the `libvirtd` app.
Justification:
snap-openstack-hypervisor packages the libvirt/nova-compute virtualization stack for OpenStack Sunbeam. On s390x, libvirt’s mediated-device (mdev) discovery reads the persistent mdevctl configuration directory at /etc/mdevctl.d to enumerate defined mediated devices. Without read access to this path, libvirtd cannot discover host-defined mdevs. The access is strictly read-only and scoped to the single /etc/mdevctl.d directory that mdevctl owns.
No existing interface covers this. libvirtd already plugs hardware-observe, mount-observe, system-observe, block-devices, kvm, and the custom microstack-support interface; none of these grant /etc/mdevctl.d. I confirmed the microstack-support definition in snapd contains no rules for /etc/mdevctl.d (or /etc generally).
Requests:
- Grant the snap declaration for the `mdevctl-config` system-files plug so the revision can pass review.
- Please also grant auto-connection for this plug. libvirtd runs as a confined system daemon and needs the access to function on fresh installs; requiring a manual `snap connect` would leave mdev discovery broken by default.
Snap: https://snapcraft.io/snap-openstack-hypervisor
Thanks!