Description of problem: ovirt-imageio-daemon requires vdsm user but it's not requiring vdsm rpm because vdsm is requiring ovirt-imageio-daemon so nothing is enforcing the correct rpm install order. If ovirt-imageio-daemon got installed, in a single transaction, before vdsm yum will report: Installing : ovirt-imageio-daemon-0.5.0-0.201612010905.git741361f.el7.centos.noarch 180/270 warning: user vdsm does not exist - using root warning: group kvm does not exist - using root and all the ovirt-imageio-daemon dirs and files will be assigned to root and this could cause runtime errors: [root@c72he20161206h1 ~]# ls -la /etc/ovirt-imageio-daemon total 16 drwxr-xr-x. 2 root root 24 Dec 6 11:57 . drwxr-xr-x. 104 root root 8192 Dec 6 11:59 .. -rw-r--r--. 1 root root 375 Dec 1 10:05 logger.conf [root@c72he20161206h1 ~]# ls -la /var/log/ovirt-imageio-daemon total 4 drwxr-xr-x. 2 root root 6 Dec 1 10:05 . drwxr-xr-x. 18 root root 4096 Dec 6 11:59 .. Version-Release number of selected component (if applicable): How reproducible: It depends from yum ordering which is currently not enforced Steps to Reproduce: 1. yum install vdsm 2. 3. Actual results: ovirt-imageio-daemon-0.5.0-0.201612010905.git741361f.el7.centos.noarch 180/270 warning: user vdsm does not exist - using root warning: group kvm does not exist - using root Expected results: no yum warnings Additional info: vdsm requires ovirt-imageio-daemon
ovirt-imageio-daemon is a helper for vdsm. Vdsm control it to allow upload to vdsm images or downloads from vdsm images. ovirt-imageio-daemon uses vdsm pki (/etc/pki/vdsm) so ovirt-imageio-proxy can access via https. We went with the easy solution, running as vdsm, and installation on a clean system was probably never tested. I think the right solution is to run ovirt-imageio-daemon on under its own user, (imageio?) so we don't have any dependency on vdsm. To allow ovirt-imageio-daemon access to vdsm pki files and images, vdsm can add the imageio user to qemu group, in vdsm-tool configure --module=imageio. This is the same way we configure sanlock.
Simple workaround: manually run yum reinstall ovirt-imageio-daemon once vdsm is there
(In reply to Nir Soffer from comment #1) > We went with the easy solution, running as vdsm, and installation on a clean > system was probably never tested. > > I think the right solution is to run ovirt-imageio-daemon on under its own > user, > (imageio?) so we don't have any dependency on vdsm. > > To allow ovirt-imageio-daemon access to vdsm pki files and images, vdsm can > add the imageio user to qemu group, in vdsm-tool configure --module=imageio. > This is the same way we configure sanlock. Sounds like a plan. Simone - given the workaround, how urgent is this? To me 4.1-beta seems like a reasonable target for this.
(In reply to Allon Mureinik from comment #3) > > I think the right solution is to run ovirt-imageio-daemon on under its own > > user, > > (imageio?) so we don't have any dependency on vdsm. > > > > To allow ovirt-imageio-daemon access to vdsm pki files and images, vdsm can > > add the imageio user to qemu group, in vdsm-tool configure --module=imageio. > > This is the same way we configure sanlock. > Sounds like a plan. Simone suggested to add a Requires(pre): vdsm - it this works, we can fix this bug *now*, and work on the more correct approach in later version.
Simone, can you check if this patch solves the issue on your setup?
Not sure why it was moved to MODIFIED, it's a 4.0.7 bug with a patch only on master, we are missing 2 backports
(In reply to Tal Nisan from comment #6) > Not sure why it was moved to MODIFIED, it's a 4.0.7 bug with a patch only on > master, we are missing 2 backports @Tal - ovirt-imageio project currently has only master branch, i.e. no branches to backport into. Can we move it to MODIFIED?
(In reply to Daniel Erez from comment #7) > (In reply to Tal Nisan from comment #6) > > Not sure why it was moved to MODIFIED, it's a 4.0.7 bug with a patch only on > > master, we are missing 2 backports > > @Tal - ovirt-imageio project currently has only master branch, i.e. no > branches to backport into. But we have downstream repositories that must include this fix - is this fix included in the downstream repositories?
(In reply to Nir Soffer from comment #8) > (In reply to Daniel Erez from comment #7) > > (In reply to Tal Nisan from comment #6) > > > Not sure why it was moved to MODIFIED, it's a 4.0.7 bug with a patch only on > > > master, we are missing 2 backports > > > > @Tal - ovirt-imageio project currently has only master branch, i.e. no > > branches to backport into. > > But we have downstream repositories that must include this fix - is this fix > included in the downstream repositories? The packages are uploaded upon release, there are no branches to backport into.
*** Bug 1400003 has been marked as a duplicate of this bug. ***
The upstream build ovirt-imageio-daemon-1.0.0-0.201612271935.git8df9ac6.el7.centos.noarch got installed successfully.
4.0.6 has been the last oVirt 4.0 release, please re-target this bug.
Verified on VDSM -> 4.19.2-2 . Engine -> ovirt-engine-4.1.0.2-0.2.el7.noarch .