Bug 1473704 - metadata update fails if preferered is null as the database schema doesn't allows null value
Summary: metadata update fails if preferered is null as the database schema doesn't al...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-manila
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 12.0 (Pike)
Assignee: Tom Barron
QA Contact: Dustin Schoenbrun
Don Domingo
URL:
Whiteboard:
Depends On:
Blocks: 1473709
TreeView+ depends on / blocked
 
Reported: 2017-07-21 13:14 UTC by Tom Barron
Modified: 2020-12-14 09:12 UTC (History)
7 users (show)

Fixed In Version: openstack-manila-5.0.0-0.20170821131529.e391476.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1469733
: 1473709 (view as bug list)
Environment:
Last Closed: 2017-12-13 21:43:17 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1703660 0 None None None 2017-07-21 13:14:37 UTC
OpenStack gerrit 482672 0 None None None 2017-07-21 13:14:37 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Comment 4 Dustin Schoenbrun 2017-11-14 20:33:30 UTC 
I was able to successfully deploy an OpenStack instance with the 2017-11-09.2 puddle while specifying a non-cluster-scoped user for the NetApp controller as well as a Storage Virtual Machine address. After the deployment, I was able to successfully create a Manila share which necessitates the insertion of correct data into Manila's database (thus the data cannot be null). The Polarion test case is linked above.
Comment 7 errata-xmlrpc 2017-12-13 21:43:17 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/RHEA-2017:3462
Note You need to log in before you can comment on or make changes to this bug.