Bug 1602981 - Missing sg_utils(command sg_scan) in openstack-cinder-volume container for cinder-backup
Summary: Missing sg_utils(command sg_scan) in openstack-cinder-volume container for ci...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-os-brick
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 13.0 (Queens)
Assignee: Eric Harney
QA Contact: Avi Avraham
Kim Nylander
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-19 00:31 UTC by Robin Cernin
Modified: 2021-12-10 16:47 UTC (History)
7 users (show)

Fixed In Version: python-os-brick-2.3.2-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-29 16:38:50 UTC
Target Upstream Version:
Embargoed:
tshefi: automate_bug+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
RDO 14900 0 None None None 2018-07-25 10:56:37 UTC
Red Hat Issue Tracker OSP-11473 0 None None None 2021-12-10 16:47:27 UTC
Red Hat Product Errata RHBA-2018:2574 0 None None None 2018-08-29 16:39:33 UTC

Description Robin Cernin 2018-07-19 00:31:58 UTC
Description of problem:

Missing sg_utils(command sg_scan) in openstack-cinder-volume container for cinder-backup

Version-Release number of selected component (if applicable):

https://access.redhat.com/containers/#/registry.access.redhat.com/rhosp13/openstack-cinder-volume/images/13.0-38

As well latest

2018-07-17 08:34:35.204 1 INFO cinder.backup.manager [req-311be1b9-9d79-4e80-b4df-6ab6e04343f2 6cf08dd6758845dbba9823eed224fe66 3461ef6361434f32891688c168cfa271 - default default] Create backup started, backup: fd698730-701c-4ae7-8526-d24e6aabe8db volume: b0830dc8-5f81-40a9-a3ec-37084549bbc0 snapshot: 9a64c262-6ac9-41f0-bd40-342d92be7245.
2018-07-17 08:36:06.098 1 ERROR oslo_messaging.rpc.server [req-311be1b9-9d79-4e80-b4df-6ab6e04343f2 6cf08dd6758845dbba9823eed224fe66 3461ef6361434f32891688c168cfa271 - default default] Exception during message handling: ProcessExecutionError: [Errno 2] No such file or directory
Command: sg_scan /dev/sde
Exit code: -
Stdout: None
Stderr: None


Actual results:

Missing sg_scan command

Expected results:

Command sg_scan should be available.

Additional info:

Comment 1 Alan Bishop 2018-07-19 12:47:10 UTC
Confirmed the problem, and it's due to os-brick not having an RPM dependency on sg3_utils.

Comment 2 Eric Harney 2018-07-19 13:35:57 UTC
Fix for RDO Rocky: https://review.rdoproject.org/r/#/c/14898/

Comment 3 Eric Harney 2018-07-23 16:03:15 UTC
RDO Queens: https://review.rdoproject.org/r/#/c/14900/

Comment 15 Tzach Shefi 2018-08-14 10:06:07 UTC
Verified on:
python2-os-brick-2.3.2-1.el7ost.noarch

On controller host as well as inside openstack-cinder-volume-docker-0 docker, now I have the missing sg_scan command. 
()[root@controller-0 /]# sg_scan 

Looks OK to verify.

Eric/Alan, sg_scan remains missing from Cinder backup's docker, is this OK? Maybe it's not needed/used inside backup docker unsure I'm just mentioning this fact before I technically verify to be on the safe side.

Comment 16 Tzach Shefi 2018-08-14 10:08:29 UTC
Wops jumped the gun on verified button by mistake. 
If sg_scan must also reside n backup docker, I'll reset bz status accordingly.

Comment 17 Joanne O'Flynn 2018-08-15 08:05:34 UTC
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.

If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".


To add draft documentation text:

* Select the documentation type from the "Doc Type" drop down field.

* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.

Comment 19 errata-xmlrpc 2018-08-29 16:38:50 UTC
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-2018:2574


Note You need to log in before you can comment on or make changes to this bug.