When shutting down a cluster node it hangs and never completes the shutdown process.

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

Environment

SUSE Linux Enterprise Server 15 SP1
SUSE Linux Enterprise High Availability Extension 15 SP1

Situation

When trying to shut down a cluster node using 'shutdown -r now', the node will hang indefinitely and requires a hard reset to get it back online.   
This only occurs when having nfs-server.service configured as a clone group in the cluster.   
If the nfs-server group is put into maintenance-mode before trying to shutdown the node, it shuts down fine. 

Resolution

Fix has been made available via a PTF and can be obtained by opening a service request.
PTF modules: 
systemd-234-24.49.2.19683.3.PTF.1169488.x86_64.rpm 
libsystemd0-32bit-234-24.49.2.19683.3.PTF.1169488.x86_64.rpm 
libsystemd0-234-24.49.2.19683.3.PTF.1169488.x86_64.rpm       
systemd-32bit-234-24.49.2.19683.3.PTF.1169488.x86_64.rpm  
systemd-sysvinit-234-24.49.2.19683.3.PTF.1169488.x86_64.rpm 

Workaround: 
1. You may take the nfs-server primitive out of a clone group and put it inside an exportfs group where it will only be loaded on one node at a time. 
or
2. Enable nfs-server.service outside the cluster and remove it from the cluster configuration until the patch update can be applied. 

Cause

When nfs-server.service is setup as a cluster resource, pacemaker will create a systemd dependency to make sure the service is shut down prior to pacemaker.service.   When this dependency is created it will do a "systemctl daemon-reload" which ends up causing a cyclical dependency on some of the systemd unit files. 
The 'var-lib-nfs-rpc_pipefs.mount -(before)-> local-fs.target' relation is inserted when a systemd daemon is reloaded.
When the system first starts, this dependency does not exist:
 # systemctl list-dependencies --before var-lib-nfs-rpc_pipefs.mount
 var-lib-nfs-rpc_pipefs.mount
 * |-nfs-idmapd.service
 * |-rpc-gssd.service
 * `-rpc-svcgssd.service

After reloading the daemon:
 # systemctl daemon-reload
 # systemctl list-dependencies --before var-lib-nfs-rpc_pipefs.mount
 var-lib-nfs-rpc_pipefs.mount
 * |-nfs-idmapd.service
 * |-rpc-gssd.service
 * |-rpc-svcgssd.service
 * `-local-fs.target

 

Additional Information

The underlying problem with daemon-reload is present on SLES12-SP4 as well.
However, the bug does not affect var-lib-nfs-rpc_pipefs.mount because its version in SLES12-SP4 does not yet contain 'After=systemd-tmpfiles-setup.service'. 
 

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:000019651
  • Creation Date: 22-Jun-2020
  • Modified Date:22-Jun-2020
    • SUSE Linux Enterprise High Availability Extension
    • SUSE Linux Enterprise Server

< 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