Bug 1459905
| Summary: | [Ganesha] : Volume export via Ganesha fails while trying to export a stopped volume,even after volume start. | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ambarish <asoman> | |
| Component: | nfs-ganesha | Assignee: | Kaleb KEITHLEY <kkeithle> | |
| Status: | CLOSED WONTFIX | QA Contact: | Ambarish <asoman> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.3 | CC: | amukherj, asoman, bturner, dang, ffilz, jthottan, kkeithle, mbenjamin, pmulay, rhinduja, rhs-bugs, skoduri, storage-qa-internal | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Known Issue | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1478647 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-11 10:11:36 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
Ambarish
2017-06-08 14:03:06 UTC
I see this in Ganesha.log : <snip> 08/06/2017 05:26:53 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] glusterfs_create_export :FSAL :EVENT :Volume testvol exported at : '/' 08/06/2017 05:26:57 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] glusterfs_get_fs :FSAL :CRIT :Unable to initialize volume. Volume: testvol 08/06/2017 05:26:58 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] mdcache_fsal_create_export :FSAL :MAJ :Failed to call create_export on underlying FSAL GLUSTER 08/06/2017 05:26:58 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] fsal_cfg_commit :CONFIG :CRIT :Could not create export for (/testvol) to (/testvol) 08/06/2017 05:26:58 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] gsh_export_addexport :EXPORT :CRIT :0 export entries in /var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf added because (export create, block validation) errors 08/06/2017 05:26:58 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] dbus_message_entrypoint :DBUS :MAJ :Method (AddExport) on (org.ganesha.nfsd.exportmgr) failed: name = (org.freedesktop.DBus.Error.InvalidFileContent), message = (0 export entries in /var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf added because (export create, block validation) errors. Details: Config File (/var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf:7): 1 validation errors in block FSAL Config File (/var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf:7): Errors processing block (FSAL) Config File (/var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf:4): 1 validation errors in block EXPORT Config File (/var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf:4): Errors found in configuration block EXPORT ) 08/06/2017 05:27:12 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] glusterfs_create_export :FSAL :EVENT :Volume testvol exported at : '/' 08/06/2017 05:27:17 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] fsal_attach_export :CONFIG :CRIT :Attaching export with out holding a reference!. hdl= = 0x0x7f57ade063d0 08/06/2017 05:27:17 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] glusterfs_create_export :FSAL :CRIT :Unable to attach export. Export: /testvol 08/06/2017 05:27:17 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] mdcache_fsal_create_export :FSAL :MAJ :Failed to call create_export on underlying FSAL GLUSTER 08/06/2017 05:27:17 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] fsal_cfg_commit :CONFIG :CRIT :Could not create export for (/testvol) to (/testvol) 08/06/2017 05:27:17 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] gsh_export_addexport :EXPORT :CRIT :0 export entries in /var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf added because (export create, block validation) errors 08/06/2017 05:27:17 : epoch 12520000 : gqas013.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-24063[dbus_heartbeat] dbus_message_entrypoint :DBUS :MAJ :Method (AddExport) on (org.ganesha.nfsd.exportmgr) failed: name = (org.freedesktop.DBus.Error.InvalidFileContent), message = (0 export entries in /var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf added because (export create, block validation) errors. Details: Config File (/var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf:7): 1 validation errors in block FSAL Config File (/var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf:7): Errors processing block (FSAL) Config File (/var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf:4): 1 validation errors in block EXPORT Config File (/var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf:4): Errors found in configuration block EXPORT </snip> I believe this is correct. Ganesha can only export active volumes. You *may* be able to start the volume, and re-export it, but that may not work. The way Ganesha is currently architected, it is not possible to export an inactive volume, start it, and expect it to show up with no further steps. (In reply to Daniel Gryniewicz from comment #4) > I believe this is correct. Ganesha can only export active volumes. You > *may* be able to start the volume, and re-export it, but that may not work. > > The way Ganesha is currently architected, it is not possible to export an > inactive volume, start it, and expect it to show up with no further steps. This seems to work on Manisha's 3.2 setup,though.without a service restart. We just tried this together on her setup,before reporting this. Is there a difference in how Gluster presents a stopped volume? If FSAL_GLUSTER is unable to do what it needs in the create_export method, and returns an error, the upper layers of Ganesha have no way to know that the volume might be available again. Add export or update export after the volume has been started should result in success (the export will not have been added even though it was in the config file originally). I really don't see any way this is other than working as designed. As part of starting the volume, glusterd (Gluster management process) invoked a hook script which sends dbus signal to export the volume. Maybe the volume was still being intialized by the time dbus signal was sent. @Ambarish, Did you try the same test case in any other 3.3 setup (using VMs)? (In reply to Soumya Koduri from comment #7) > As part of starting the volume, glusterd (Gluster management process) > invoked a hook script which sends dbus signal to export the volume. Maybe > the volume was still being intialized by the time dbus signal was sent. > > @Ambarish, > > Did you try the same test case in any other 3.3 setup (using VMs)? Cannot repro on 3.3 VMs. Ambarish, Could you please share the setup as we are unable to reproduce this issue. |