Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1358520 - Backport: Bug “Dell SC: Wrong replication syncmode specified” (1596680)
Summary: Backport: Bug “Dell SC: Wrong replication syncmode specified” (1596680)
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ga
: 9.0 (Mitaka)
Assignee: Eric Harney
QA Contact: lkuchlan
Depends On: 1351271 1358513
TreeView+ depends on / blocked
Reported: 2016-07-20 21:39 UTC by Rajini Karthik
Modified: 2019-02-17 03:54 UTC (History)
28 users (show)

Fixed In Version: openstack-cinder-8.0.0-5.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1358513
Last Closed: 2016-08-24 12:56:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Launchpad 1596680 None None None 2016-08-03 14:52:19 UTC
Red Hat Product Errata RHBA-2016:1760 normal SHIPPED_LIVE openstack-cinder bug fix advisory 2016-08-24 16:49:58 UTC

Description Rajini Karthik 2016-07-20 21:39:08 UTC
Description of problem:
Backport this bug into stable mitaka ( yet TBD)
And pull this into OSP9
Bug “Dell SC: Wrong replication syncmode specified” (1596680)

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Rajini Karthik 2016-07-21 13:09:50 UTC
Cherry pick for stable/mitaka

Comment 4 errata-xmlrpc 2016-08-24 12:56:07 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.

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