Ganesha manager service initialization fails if ganesha exports directory is empty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Undecided
|
Ramana Raja |
Bug Description
During initialization of the ganesha manager service the exports are reset i.e., ganesha export files are removed from the
ganesha exports directory. When no files are present in the ganesha exports directory (by default /etc/ganesha/
TRACE manila.service File "/opt/stack/
TRACE manila.service self.driver.
TRACE manila.service File "/opt/stack/
TRACE manila.service self._setup_
TRACE manila.service File "/opt/stack/
TRACE manila.service helper.
TRACE manila.service File "/opt/stack/
TRACE manila.service ganesha_
TRACE manila.service File "/opt/stack/
TRACE manila.service self.reset_
TRACE manila.service File "/opt/stack/
TRACE manila.service 'rm %s/*.conf' % pipes.quote(
TRACE manila.service File "/opt/stack/
TRACE manila.service cmd=e.cmd)
TRACE manila.service GaneshaCommandF
TRACE manila.service Command: sudo manila-rootwrap /etc/manila/
TRACE manila.service Exit code: 1
TRACE manila.service Stdout: u''
TRACE manila.service Stderr: u"rm: cannot remove '/etc/ganesha/
Changed in manila: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in manila: | |
milestone: | kilo-2 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/151994
Review: https:/