System with FCoE connected devices fails to boot randomly due to wicked ordering cycle problems

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

Environment

SUSE Linux Enterprise Server for SAP Applications 15 SP2
SUSE Linux Enterprise Server 15 SP2


Situation

Booting a system with Fibre Channel over Ethernet (FCoE) connected devices result in random boot failures. Analyzing the journalctl -xb output, the wicked service reports messages similar to:
 

Aug 24 13:43:27 sles15sp2 systemd[1]: wickedd.service: Job wickedd.service/start deleted to break ordering cycle starting with network.target/start
Aug 24 13:43:27 sles15sp2 systemd[1]: network.target: Found dependency on wickedd-dhcp6.service/start
Aug 24 13:43:27 sles15sp2 systemd[1]: network.target: Breaking ordering cycle by deleting job wickedd-dhcp6.service/start
Aug 24 13:43:27 sles15sp2 systemd[1]: wickedd-dhcp6.service: Job wickedd-dhcp6.service/start deleted to break ordering cycle starting with network.target/start

Aug 24 13:43:27 sles15sp2 systemd[1]: Starting wicked network nanny service...
Aug 24 13:43:27 sles15sp2 wickedd-nanny[1513]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds:
Aug 24 13:43:27 sles15sp2 wickedd-nanny[1513]: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files
Aug 24 13:43:27 sles15sp2 wickedd-nanny[1513]: Couldn't refresh list of active network interfaces
Aug 24 13:43:27 sles15sp2 systemd[1]: Starting wicked DHCPv4 supplicant service...
Aug 24 13:43:27 sles15sp2 systemd[1]: Starting wicked AutoIPv4 supplicant service...
Aug 24 13:43:27 sles15sp2 systemd[1]: Started wicked network nanny service.
Aug 24 13:43:27 sles15sp2 systemd[1]: Started wicked DHCPv4 supplicant service.
Aug 24 13:43:27 sles15sp2 systemd[1]: Started wicked AutoIPv4 supplicant service.



Checking /etc/fstab a configuration with several mount points and /var on a separate volume is observed, the mount points are configured to use the _netdev option like:

/dev/evg00/root                            /                  xfs   defaults      0  0
/dev/evg00/var                             /var               xfs   _netdev       0  0
/dev/evg00/var.tmp                         /var/tmp           xfs   nodev,nosuid  0  0
/dev/evg00/var.log                         /var/log           xfs   _netdev       0  0
/dev/evg00/var.crash                       /var/crash         xfs   _netdev       0  0
/dev/evg00/usr                             /usr               xfs   _netdev       0  0
/dev/evg00/tmp                             /tmp               xfs   nodev,nosuid  0  0
/dev/evg00/opt                             /opt               xfs   _netdev       0  0
/dev/evg00/swap                            swap               swap  _netdev       0  0

Resolution

To address this issue, please apply the fix SUSE-SLE-Module-Basesystem-15-SP2-2021-698. To have the fix available during installation, the Installer Self-Update repository needs to be enabled as patches required for the installation environment. For further details, please see:

https://documentation.suse.com/sles/15-SP2/html/SLES-all/cha-install.html#sec-yast-install-self-update

Cause

YaST2 used to rely on the transport class of connected hardware to determine whether the _netdev option was required. Adding it automatically during installation caused a mount delay for the /var volume which is used by several services to store temporary data. However, the _netdev option instructs the kernel to wait until the network has been activated. This creates a race condition and the system fails to boot properly.

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:000019889
  • Creation Date: 04-Mar-2021
  • Modified Date:04-Mar-2021
    • 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