Bug 1343140
| Summary: | manila-dist.conf is empty | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eric Harney <eharney> |
| Component: | openstack-manila | Assignee: | Victoria Martinez de la Cruz <vimartin> |
| Status: | CLOSED ERRATA | QA Contact: | Dustin Schoenbrun <dschoenb> |
| Severity: | unspecified | Docs Contact: | Don Domingo <ddomingo> |
| Priority: | unspecified | ||
| Version: | 10.0 (Newton) | CC: | dschoenb, egafford, jjoyce, jschluet |
| Target Milestone: | beta | Keywords: | Triaged |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-manila-3.0.0-0.20160903135125.7a16eb6.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-14 15:36:11 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: | |||
|
Description
Eric Harney
2016-06-06 15:26:08 UTC
Does Manila use oslo_config_generator? If so, this should be autogenerated in the packaging process. I checked upstream in master and it looks like there is support for oslo_config_generator [1]. However, it looks like the only output of it would be the sample manila.conf file. Looks like the manila-dist.conf is not being generated by it. I imagine we could look at how other projects do it and add the same to Manila? [1] - https://github.com/openstack/manila/tree/master/etc/oslo-config-generator Using the 2016-10-06.1 puddle, I was able to log into a controller node and then look at the /usr/share/manila/manila-dist.conf file which was present and had valid content in it. Looks good to me! 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://rhn.redhat.com/errata/RHEA-2016-2948.html |