Bug 1128460
Summary: | Staypuft deployment with NFS backend for Cinder doesn't fill the share on the config file | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Ido Ovadia <iovadia> | ||||
Component: | rubygem-staypuft | Assignee: | Scott Seago <sseago> | ||||
Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 5.0 (RHEL 6) | CC: | mburns, tshefi, yeylon | ||||
Target Milestone: | ga | Keywords: | Regression | ||||
Target Release: | Installer | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | ruby193-rubygem-staypuft-0.2.5-1.el6ost | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-08-21 18:08:45 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Ido Ovadia
2014-08-10 15:48:31 UTC
Created attachment 925775 [details]
Screenshot or setting
Testing this again today, my deployment failed due to other reason. Looking around on Advanced configuration tab under cinder nfs I noticed: Cinder nfs shares [] Cinder nfs mount options nosharecache Note first one is blank, yet I'm sure I configured Cinder nfs usage (192.168.0.1:/cinder), is this expected or related to this bug? Attached screen shoot comment 3. Verified with: ruby193-rubygem-staypuft-0.2.5-1.el6ost.noarch ( puddle 2014-08-15.1) vi /etc/cinder/shares-nfs.conf --> 192.168.0.1:/cinder 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. http://rhn.redhat.com/errata/RHBA-2014-1090.html |