Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1473704 - metadata update fails if preferered is null as the database schema doesn't allows null value
metadata update fails if preferered is null as the database schema doesn't al...
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-manila (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
medium Severity medium
: rc
: 12.0 (Pike)
Assigned To: Tom Barron
Dustin Schoenbrun
Don Domingo
: Triaged
Depends On:
Blocks: 1473709
  Show dependency treegraph
 
Reported: 2017-07-21 09:14 EDT by Tom Barron
Modified: 2018-02-05 14:10 EST (History)
7 users (show)

See Also:
Fixed In Version: openstack-manila-5.0.0-0.20170821131529.e391476.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1469733
: 1473709 (view as bug list)
Environment:
Last Closed: 2017-12-13 16:43:17 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1703660 None None None 2017-07-21 09:14 EDT
OpenStack gerrit 482672 None None None 2017-07-21 09:14 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Comment 4 Dustin Schoenbrun 2017-11-14 15:33:30 EST
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 16:43:17 EST
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.