DeepSea stage 4 fails when there are NFS Ganesha changes

This document (7023578) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Enterprise Storage 5
SUSE Enterprise Storage 5.5


Situation

When making changes to the NFS Ganesha configuration, for example adding and / or removing nodes, running stage 4 to implement the changes fails for each configured Ganesha node with:

ganesha_node.hwlab.suse.de:
----------
       ID: wait for all processes
    Function: module.run
      Name: cephprocesses.wait
     Result: False
     Comment: Module function cephprocesses.wait executed
     Started: 16:48:32.313124
     Duration: 135277.053 ms
      Changes:   
          ----------
          ret:
            False

When looking directly on the node, no changes were made and none of the Ganesha RPMs were installed.

Resolution

The current workaround is to run the Ganesha stage directly by executing:

# salt-run state.orch ceph.stage.ganesha

Cause

Missing jinja conditional in the main Ganesha configuration file.

Additional Information

Note that when running the Ganesha stage directly, the following error will still be seen for the designated Ganesha nodes:

[ERROR   ] Run failed on minions: vm-hanode1.hwlab.suse.de, vm-hanode2.hwlab.suse.de
Failures:
    vm-hanode1.hwlab.suse.de:
      Name: /var/lib/ceph/radosgw/ceph-ganesha.vm-hanode1/keyring - Function: file.managed - Result: Changed Started: - 16:58:28.630072 Duration: 1052.463 ms                                                                                                                              
      Name: zypper --non-interactive in nfs-ganesha nfs-ganesha-ceph nfs-ganesha-rgw nfs-ganesha-utils - Function: cmd.run - Result: Changed Started: - 16:58:29.695013 Duration: 3756.317 ms                                                                                              
    ----------
              ID: /etc/ganesha/ganesha.conf
        Function: file.managed
          Result: False
         Comment: Source file salt://ceph/ganesha/cache/ganesha.vm-hanode1.conf not found
         Started: 16:58:33.451538
        Duration: 4.381 ms


The above error is not critical, the relevant conf file will be created once a new NFS export is created via openATTIC for the relevant Ganesha nodes.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7023578
  • Creation Date: 12-Dec-2018
  • Modified Date:03-Mar-2020
    • SUSE Enterprise Storage

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center