Hide Forgot
Description of problem: Setup of Cinder backend to Glance according to RFE https://bugzilla.redhat.com/show_bug.cgi?id=1293435 fails because of missing configuration to rootwrap Version-Release number of selected component (if applicable): python-glance-13.0.0-1.el7ost.noarch openstack-glance-13.0.0-1.el7ost.noarch python-glance-store-0.18.1-0.20161003180701.4e144bb.el7ost.noarch puppet-glance-9.4.0-1.el7ost.noarch python-glanceclient-2.5.0-1.el7ost.noarch How reproducible: Steps to Reproduce: 1. Login to controller server of the overcloud environment 2. cd /etc/glance 3. ls -l rootwrap.* Actual results: ls: cannot access rootwarp.*: No such file or directory Expected results: -rwxr-xr-x. 1 root glance 973 Nov 10 14:34 rootwrap.conf rootwrap.d: total 4 -rwxr-xr-x. 1 root glance 1265 Nov 10 14:24 glance_cinder_store.filters Additional info:
https://review.rdoproject.org/r/#/c/3794/
Moving to ON_DEV as patch is posted.
(In reply to Eric Harney from comment #1) > https://review.rdoproject.org/r/#/c/3794/ Mostly reverted at https://review.rdoproject.org/r/#/c/5658/ .
As stated by Eric, we'll try to fix this for OSP12.
Moving to OSP12
Before I verify on: python-glance-store-0.21.0-0.20170720000947.599b9b8.el7ost.noarch ()[glance@controller-0 /etc/glance]$ ls -l rootwrap.* total 0 lrwxrwxrwx. 1 root root 45 Aug 2 20:33 os-brick.filters -> /usr/share/os-brick/rootwrap/os-brick.filters Cyril, is this sufficient to verify? As I don't see exact files which we at least thought would show up according to Avi's initial bug report. Expected results: -rwxr-xr-x. 1 root glance 973 Nov 10 14:34 rootwrap.conf -> in our case we only have rootwrap.d (folder not a file) rootwrap.d: total 4 -rwxr-xr-x. 1 root glance 1265 Nov 10 14:24 glance_cinder_store.filters Again in our case rather than a file by this ^ name, we have a symlink called: os-brick.filters I am almost sure its fine, just want to verify with you before officially verifying.
@Tzach: No, we need the "rootwrap.conf" file added by this patch: https://review.openstack.org/#/c/485244
Cyril, As mentioned above we must also have that missing rootwrap.conf file, noticed upstream code got merged, great. But now I'm even more confused, what am I missing here? If code landed downstream, assume it did as we have a fixed-in/ON_QA state, right? I should fail verification, as code didn't produce missing file reset bug status to assigned? Or should I keep it ON_QA till we get a new downstream/fixed-in version? Which would hopefully create the missing rootwrap.conf file?
I'm not sure whether the rootwrap.conf file (merged upstream) is already available downstream, because I have no idea how the whole upstream -> RDO -> OSP12 thing works. If the rootwrap.conf file is not there, this won't work.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462