sysfsutils is a requirement for python-os-brick 2.3.4-2 on OSP13 and 2.5.5-1 on OSP14. Which version is installed here?
The issue was present in 14z1, and the fix will be in the upcoming 14z2 release.
Verified on: python2-os-brick-2.5.6-1.el7ost.noarch puppet-glance-13.3.2-0.20190420084238.45584f0.el7ost.noarch openstack-tripleo-heat-templates-9.3.1-0.20190513171725.9995be9.el7ost.noarch On a pre existing system where Cinder used 3par FC backend. I'd added below yaml to overcloud_deploy.sh: Cat /home/stack/bm/extra_templates.yaml --- parameter_defaults: GlanceBackend: cinder Once overcloud update had completed we noticed the two missing libs under Glance docker: ()[glance@controller-0 /]$ rpm -qa | grep sysfsutils- sysfsutils-2.1.0-16.el7.x86_64 ()[glance@controller-0 /]$ rpm -qa | grep libsysfs- libsysfs-2.1.0-16.el7.x86_64 I'd also uploaded a new image to Glance. As can be seen the image was successfully uploaded to Glance using a Cinder backend. (overcloud) [stack@puma52 ~]$ glance image-create --name CirrosCinder --file cirros-0.4.0-x86_64-disk.img --disk-format qcow2 --container-format bare +------------------+----------------------------------------------------------------------------------+ | Property | Value | +------------------+----------------------------------------------------------------------------------+ | checksum | 443b7623e27ecf03dc9e01ee93f67afe | | container_format | bare | | created_at | 2019-06-09T02:01:28Z | | direct_url | cinder://b8a9b7a7-093a-41fc-8147-108926177daf | | disk_format | qcow2 | | id | 2faf43ef-946f-44f5-8273-f8a0f81d8f66 | | min_disk | 0 | | min_ram | 0 | | name | CirrosCinder | | os_hash_algo | sha512 | | os_hash_value | 6513f21e44aa3da349f248188a44bc304a3653a04122d8fb4535423c8e1d14cd6a153f735bb0982e | | | 2161b5b5186106570c17a9e58b64dd39390617cd5a350f78 | | os_hidden | False | | owner | aa14945a4e6e4dc8ba7471d2c7d73c06 | | protected | False | | size | 12716032 | | status | active | | tags | [] | | updated_at | 2019-06-09T02:02:16Z | | virtual_size | Not available | | visibility | shared | +------------------+----------------------------------------------------------------------------------+ Created a Cinder volume from this image (overcloud) [stack@puma52 ~]$ cinder create 2 --image CirrosCinder --name CindeVolFromImageOnCinder +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | attachments | [] | | availability_zone | nova | | bootable | false | | consistencygroup_id | None | | created_at | 2019-06-09T02:13:43.000000 | | description | None | | encrypted | False | | id | 78787ae6-9365-4538-9af7-868f8fa7c718 | | metadata | {} | | migration_status | None | | multiattach | False | | name | CindeVolFromImageOnCinder | | os-vol-host-attr:host | controller-0@3parfc#SSD_r5 | | os-vol-mig-status-attr:migstat | None | | os-vol-mig-status-attr:name_id | None | | os-vol-tenant-attr:tenant_id | aa14945a4e6e4dc8ba7471d2c7d73c06 | | replication_status | None | | size | 2 | | snapshot_id | None | | source_volid | None | | status | creating | | updated_at | 2019-06-09T02:13:44.000000 | | user_id | b57c5d2f15b142439df17f09ef157dcd | | volume_type | tripleo | +--------------------------------+--------------------------------------+ (overcloud) [stack@puma52 ~]$ cinder list +--------------------------------------+-----------+---------------------------+------+-------------+----------+--------------------------------------+ | ID | Status | Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+-----------+---------------------------+------+-------------+----------+--------------------------------------+ | 78787ae6-9365-4538-9af7-868f8fa7c718 | available | CindeVolFromImageOnCinder | 2 | tripleo | true | | Looks good to verify, we have both missing libs in Glance Docker. We see that Glance successfully uses Cinder as backend.
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/RHBA-2019:1672