systemd doesn't unmount the NFS shares before stopping network

Bug #1697752 reported by Marc Methot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Unassigned

Bug Description

When rebooting controllers, the nodes all hang and require a reset via Console to complete reboot. Once you do this one time, the following reboots will all be successful.

This was found to be caused by the auto dependencies systemd-fstab-generator, in this case we should add the mount option '_netdev'

Mount units referring to local and network file systems are distinguished by their file system type specification. In some cases this is not sufficient (for example network block device based mounts, such as iSCSI), in which case _netdev may be added to the mount option string of the unit, which forces systemd to consider the mount unit a network mount. Mount units (regardless if local or network) also acquire automatic Before= and Conflicts= on umount.target in order to be stopped during shutdown.

Marc Methot (mb-methot)
affects: puppet-midonet → puppet-tripleo
Changed in puppet-tripleo:
assignee: nobody → Marc (mb-methot)
no longer affects: puppet-tripleo
Changed in tripleo:
importance: Undecided → Medium
status: New → Triaged
milestone: none → pike-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-tripleo (master)

Reviewed: https://review.openstack.org/473951
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=96c4adecb2b6ff51d1a3b63a4219e107d0172d1b
Submitter: Jenkins
Branch: master

commit 96c4adecb2b6ff51d1a3b63a4219e107d0172d1b
Author: Marc Methot <email address hidden>
Date: Tue Jun 13 15:23:54 2017 -0400

    Fixes an issue when rebooting with an NFS mount.

    _netdev mount option helps fix a timing issue when rebooting.
    This looks like we're hitting an issue where we're using
    network instead of NetworkManager and that systemd doesn't
    unmount the NFS shares before stopping network.

    Change-Id: I5d2c89db29ef75aaf371b3c9dd561587d7b6f87b
    Closes-Bug: #1697752

Changed in tripleo:
status: Triaged → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-tripleo 7.2.0

This issue was fixed in the openstack/puppet-tripleo 7.2.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.