> when attaching new volume to host. systemd-udevd trigger
> unshare process to run snap import command on new volumes and it fail.
> volume finally map to host. it doesn't affect volume usage.
> but some udev rule need to check for this strange behavior.
Please correct me if I'm wrong, but it seems the issue is only
a concern about the command failure status logged, and there's
no functional issue; is that correct?
Hi Vincent,
Thanks for the bug report.
> when attaching new volume to host. systemd-udevd trigger
> unshare process to run snap import command on new volumes and it fail.
> volume finally map to host. it doesn't affect volume usage.
> but some udev rule need to check for this strange behavior.
Please correct me if I'm wrong, but it seems the issue is only
a concern about the command failure status logged, and there's
no functional issue; is that correct?