Bug 1484040 - openstack-cinder needs higher os-brick minimum dependency
Summary: openstack-cinder needs higher os-brick minimum dependency
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z3
: 11.0 (Ocata)
Assignee: Eric Harney
QA Contact: Avi Avraham
URL:
Whiteboard:
Depends On:
Blocks: 1445192
TreeView+ depends on / blocked
 
Reported: 2017-08-22 13:55 UTC by Eric Harney
Modified: 2017-10-31 17:44 UTC (History)
6 users (show)

Fixed In Version: openstack-cinder-10.0.4-3.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-31 17:44:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3103 0 normal SHIPPED_LIVE openstack-cinder bug fix advisory 2017-10-31 21:40:20 UTC

Description Eric Harney 2017-08-22 13:55:02 UTC
After changes made in bug 1445192, openstack-cinder requires os-brick >= 1.11.0-2.

This needs to be added to prevent compatibility problems between cinder and brick with the recent multipath changes.

Version-Release number of selected component (if applicable):
openstack-cinder-10.0.3-3.el7ost

Comment 4 Tzach Shefi 2017-10-15 15:39:33 UTC
Verified on: 
openstack-cinder-10.0.6-1.el7ost.noarch

Os brick is older than minimum version. 
python-os-brick-1.11.0-5.el7ost.noarch

To actually verify/find the minimum dependency mention:

1. yum -q deplist openstack-cinder-10.0.6-1.el7ost.noarch
package: openstack-cinder.noarch 1:10.0.6-1.el7ost

... 

2. Test all sub dependence from above list, till I hit the jackpot ->   


yum -q deplist python-cinder-10.0.6-1.el7ost.noarch | grep brick
  dependency: os-brick >= 1.11.0-2    -> verified.  
   provider: python-os-brick.noarch 1.11.0-5.el7ost

Comment 6 errata-xmlrpc 2017-10-31 17:44:20 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-2017:3103


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