Shutdown hangs with active iscsi sessions

[Matt Schulte]

This is a duplicate of the bug listed here: https://bugs.launchpad.net/bugs/1569925 for 16.04.

That bug was automatically closed though the problem still persists. I am opening this bug for 16.10 in hopes that it will catch somebody's attention.

I have 4 servers running the latest 16.10 updates.

Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper.

While logged into the iscsi sessions all I have to do is reboot the server and I get a hang.

I see a message that says:

  "Reached target Shutdown"

followed by

  "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

and then I see 8 lines that say:

  "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***"
  "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***"
  "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***"
  "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***"
  "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***"
  "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***"
  "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***"
  "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***"
  NOTE: the actual values of the *'s differ for each line above.

Screenshot of the issue:
https://www.dropbox.com/s/93mv7cj8asspcpa/ShutdownCapture.JPG?dl=0

~# lsb_release -rd
Description: Ubuntu 16.10
Release: 16.10

~# apt-cache policy open-iscsi
open-iscsi:
  Installed: 2.0.873+git0.3b4b4500-14ubuntu8
  Candidate: 2.0.873+git0.3b4b4500-14ubuntu8
  Version table:
 *** 2.0.873+git0.3b4b4500-14ubuntu8 500
        500 http://repomirror-ict.eng.netapp.com/ubuntu yakkety/main amd64 Packages
        100 /var/lib/dpkg/status

~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eno1
iface eno1 inet dhcp
# This is an autoconfigured IPv6 interface
iface eno1 inet6 auto

# This is an autoconfigured interface
auto enp4s0
iface enp4s0 inet static
 address 192.12.21.2
 netmask 255.255.255.0
 mtu 9000
# This is an autoconfigured interface
auto enp130s0f3
iface enp130s0f3 inet static
 address 192.12.22.2
 netmask 255.255.255.0
 mtu 9000

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Matt Schulte (gimpyestrada)]

Any movement here?

[Matt Schulte (gimpyestrada)]

Installed the most recent build of Zesty (zesty-server-amd64.iso 2017-02-22 06:54 676M).

I was able to:

1. Confirm the issue still exists.
2. Confirm that the issue is not caused by multipath (i.e. it still occurs during reboot when multipathing is disabled).

[Dan Streetman (ddstreet)]

please reopen if this is still an issue