[Bug 208183] Re: bcm4328 chipset not supported by hardy heron

[Matt Schulte]

I also have the BCM4328 (Rev 03) chipset.  It is not detected by the
default Hardy 8.04 install, as advertised.

Likewise I have had some success with the ndiswrapper.  I have a Dell
Inspiron 1721, and am using an XP driver that I found on their website.

I don't have a lot of experience with ndiswrapper, so I don't know if
this is to be expected, but it seems to take an inordinate amount of
time for the wireless to connect up and get an ip address.

-- 
bcm4328 chipset not supported by hardy heron
https://bugs.launchpad.net/bugs/208183
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 249340] Re: Gutsy-Hardy upgrade hangs in localedef

[Matt Schulte]

I am upgrading from 7.10 to 8.04 LTS with 2.6.22-16-server.

Using the upgrade manager the upgrade has been completed without a
problem.

-- 
Gutsy-Hardy upgrade hangs in localedef
https://bugs.launchpad.net/bugs/249340
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx

[Matt Schulte]

Here is an example of a bunch of failover events from a rebooted storage
controller.  You can see that there are others similar to what you
mentioned above.

** Attachment added: "syslog containing failover"
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+attachment/4680426/+files/syslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570093

Title:
  multipath-tools update introduced syslog messages about partx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx

[Matt Schulte]

This is the output of multipathd show config, which is the effective
multipath.conf file.

** Attachment added: "multipath.config"
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+attachment/4680592/+files/multipath.config

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570093

Title:
  multipath-tools update introduced syslog messages about partx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx

[Matt Schulte]

I have no multipath.conf, we just use the defaults that are built in for
our storage.

multipath -ll for that particular host is not going to look good right
now as I'm having an issue with an Emulex device.  Until I get my
hardware issue resolved I don't want to send you an output that will be
confusing as I only have one path right now :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570093

Title:
  multipath-tools update introduced syslog messages about partx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1586528] [NEW] Avahi-daemon withdraws address record

[Matt Schulte]

Public bug reported:

For some reason, if I leave my Ubuntu VM up for a prolonged period of
time the machine will lose connection to the network.  ip addr shows
that the nic port no longer has an address and an examination of the
syslog shows this:

May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group 
on interface enp0s3.IPv4 with address 10.0.2.15.
May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.


for no known reason.

The only reliable way to get the network to come back (that I have
found) is a full reboot.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 27 15:11:34 2016
InstallationDate: Installed on 2015-10-22 (218 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: avahi
UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

** Affects: avahi (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586528

Title:
  Avahi-daemon withdraws address record

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

I have finally been able to verify that this is reproducible with the
released 16.04 from the ISO.

What else can be provided here to move this bug along?

(This is being tracked internally in CQ 860251)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1586528] Re: Avahi-daemon withdraws address record

[Matt Schulte]

Maybe the problem is not in Avahi, but it is still a problem somewhere.

This bug continues to plague my vm.  Today I noticed that if I try to
interact with the network port, I am told that it is  unknown, does this
have something to do with it?


matt@matt-VirtualBox:~$ ip addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: enp0s3:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether 08:00:27:77:bd:5b brd ff:ff:ff:ff:ff:ff
inet6 fe80::ac78:e0ca:b9f3:5266/64 scope link 
   valid_lft forever preferred_lft forever
matt@matt-VirtualBox:~$ ifdown enp0s3
Unknown interface enp0s3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586528

Title:
  Avahi-daemon withdraws address record

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1565969] [NEW] Udev rule causes automatic incorrect unmount of dm device

[Matt Schulte]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd'

Description: Ubuntu Xenial Xerus (development b ranch)
Release: 16.04

2) The version of the package you are using, via 'apt-cache policy
pkgname'

systemd:
  Installed: 229-3ubuntu1
  Candidate: 229-3ubuntu1

3) What you expected to happen

I am testing our E-Series Netapp storage array and the ability of the
server to failover IO to the secondary path.  I pull a cable and allow
DM-MP to fail the path and route IO down the other path.  I then replug
the cable and repeat for the other path.

I expect that the failover to occur and for the mount points to stay
mounted through the operation.

4) What happened instead

I see in the system log that during the test systemd tries to perform an
unmount operation on the mountpoint of the dm-device(s) that have lost
an underlying path.  The unmount fails, I assume because there is active
IO at the time.  However it should not be attempted in the first place.

I believe this is related to the bug that we discovered in RHEL and SLES
that can be seen in this redhat commit:

https://github.com/lnykryn/systemd-
rhel/commit/d77ced281c6d1f47b5dfc3abff6817d8f5756af9

Our testing of RHEL seems to indicate that this patch resolved our
problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Mon Apr  4 13:56:35 2016
MachineType: Dell Inc. PowerEdge R720
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=ab1330f8-0a76-4ba4-b2a2-a55f2b68b8c0 ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service -> 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service -> 
/lib/systemd/system/rc-local.service.d/debian.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/22/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.4
dmi.board.name: 0VWT90
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.4:bd01/22/2016:svnDellInc.:pnPowerEdgeR720:pvr:rvnDellInc.:rn0VWT90:rvrA02:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R720
dmi.sys.vendor: Dell Inc.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

[Matt Schulte]

This bug is being tracked in Netapp's internal bug tracking system:
LSIP200858428

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] [NEW] Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Public bug reported:

I have 4 servers running the latest 16.04 updates from the development
branch (as of right now).

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.

This seems like a bug somewhere but I am unaware of any additional
logging that I could turn on to pinpoint the problem.

Note I also have similar setups that are not doing iscsi and they don't
have this problem.

Here is a screenshot of what I see on the shell when I try to reboot:

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

This is being tracked in NetApp bug tracker CQ number 860251.

If I log out of all iscsi sessions before rebooting then I do not
experience the hang:

iscsiadm -m node -U all

We are wondering if this could be some kind of shutdown ordering
problem.  Like the network devices have already disappeared and then
iscsi tries to perform some operation (hence the ping timeouts).

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] [NEW] Continuous messages from systemd: dm disk appears twice

[Matt Schulte]

Public bug reported:

I have 4 servers running the latest 16.04 updates from the development
branch (as of right now).

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 running IO to the iscsi targets my system log is flooded with
messages that look like this:

Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-scsi\x2d360080e50002909248d765605fa52.device: Dev 
dev-disk-by\x2did-scsi\x2d360080e50002909248d765605fa52.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host21/session8/target21:0:0/21:0:0:9/block/sdbh and 
/sys/devices/virtual/block/dm-59
Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-wwn\x2d0x60080e50002909248d765605fa52.device: Dev 
dev-disk-by\x2did-wwn\x2d0x60080e50002909248d765605fa52.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host19/session6/target19:0:0/19:0:0:9/block/sdcd and 
/sys/devices/virtual/block/dm-59
Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-scsi\x2d360080e5000290924993956f4a1cb.device: Dev 
dev-disk-by\x2did-scsi\x2d360080e5000290924993956f4a1cb.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host21/session8/target21:0:0/21:0:0:121/block/sdej and 
/sys/devices/virtual/block/dm-37
Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-wwn\x2d0x60080e5000290924993956f4a1cb.device: Dev 
dev-disk-by\x2did-wwn\x2d0x60080e5000290924993956f4a1cb.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host19/session6/target19:0:0/19:0:0:121/block/sdfk and 
/sys/devices/virtual/block/dm-37
Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-scsi\x2d360080e50002909248d805605fa8b.device: Dev 
dev-disk-by\x2did-scsi\x2d360080e50002909248d805605fa8b.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host20/session7/target20:0:0/20:0:0:19/block/sdel and 
/sys/devices/virtual/block/dm-50
Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-wwn\x2d0x60080e50002909248d805605fa8b.device: Dev 
dev-disk-by\x2did-wwn\x2d0x60080e50002909248d805605fa8b.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host19/session6/target19:0:0/19:0:0:19/block/sdew and 
/sys/devices/virtual/block/dm-50
Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-scsi\x2d360080e50002909248d785605fa5e.device: Dev 
dev-disk-by\x2did-scsi\x2d360080e50002909248d785605fa5e.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host18/session5/target18:0:0/18:0:0:11/block/sdcb and 
/sys/devices/virtual/block/dm-35
Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-wwn\x2d0x60080e50002909248d785605fa5e.device: Dev 
dev-disk-by\x2did-wwn\x2d0x60080e50002909248d785605fa5e.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host20/session7/target20:0:0/20:0:0:11/block/sdcj and 
/sys/devices/virtual/block/dm-35
Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-scsi\x2d360080e50002909248d7a5605fa6a.device: Dev 
dev-disk-by\x2did-scsi\x2d360080e50002909248d7a5605fa6a.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host20/session7/target20:0:0/20:0:0:13/block/sdcw and 
/sys/devices/virtual/block/dm-44
Apr  8 11:48:36 ICTM1612S02H2 systemd[1]: 
dev-disk-by\x2did-wwn\x2d0x60080e50002909248d7a5605fa6a.device: Dev 
dev-disk-by\x2did-wwn\x2d0x60080e50002909248d7a5605fa6a.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host21/session8/target21:0:0/21:0:0:13/block/sdcf and 
/sys/devices/virtual/block/dm-44

It seems that systemd doesn't know what to do with dm devices and its
"disk-by" simlinks.

This is being tracked in NetApp bug tracker CQ number 860309.

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  Continuous messages from systemd: dm disk appears twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

[Matt Schulte]

Can you comment on when or if this fixed package might be pushed to the
Xenial repos?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Contents of fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
UUID=3f62d8b3-3afe-4cd7-8d36-49101b1d7b02 /   ext4
errors=remount-ro 0   1
# swap was on /dev/sda5 during installation
UUID=9c54f202-7e90-4633-9134-706e6d7080fc noneswapsw
  0   0
10.113.242.59:/IOP  /opt/iopnfs noauto  
0 0

#IOMNT START#
/dev/mapper/3600a09800059d66afa5c56f3e78f   
/iomnt-3600a09800059d66afa5c56f3e78fext3
nobarrier,_netdev   0 0
/dev/mapper/3600a09800059d7b4223656f3ef42   
/iomnt-3600a09800059d7b4223656f3ef42ext4
nobarrier,_netdev,discard   0 0
/dev/mapper/3600a09800059d66afa5456f3e782   
/iomnt-3600a09800059d66afa5456f3e782xfs 
nobarrier,_netdev,discard   0 0
/dev/mapper/3600a09800059d66afa5056f3e77b   
/iomnt-3600a09800059d66afa5056f3e77bbtrfs   
nobarrier,_netdev,discard   0 0
/dev/mapper/360080e50003415e6147d5605f7fb   
/iomnt-360080e50003415e6147d5605f7fbext3
nobarrier,_netdev   0 0
/dev/mapper/360080e500034153eed065605faa2   
/iomnt-360080e500034153eed065605faa2ext4
nobarrier,_netdev,discard   0 0
#IOMNT END#

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

This contains the configuration of my iscsi sessions.  It is a tar of
the entire /etc/iscsi folder, it should show what we've got going on.

** Attachment added: "iscsi.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4648082/+files/iscsi.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Here is the requested journal.txt file.

I had a bit of difficulty after performing the requested operations, my
server kept booting into the (initramfs) prompt.

The journal log may contain more than one reboot attempt.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4648081/+files/journal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

And just for good measure this is my /etc/network/interfaces file:

# 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

auto enp130s0
iface enp130s0 inet6 static
address fe80::192:12:21:115
netmask 64
mtu 9000

auto enp4s0f0
iface enp4s0f0 inet6 static
address fe80::192:12:22:115
netmask 64
mtu 9000

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

I definitely have remote filesystems mounted (using _netdev if that
matters) when I experience this problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: Continuous messages from systemd: dm disk appears twice

[Matt Schulte]

I think I missed some questions.  I'll try to aggregate:

1. Contents of "/proc/cmdline"
   BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic 
root=UUID=584a6a87-26b5-4262-b316-ca9d1c3a8a20 ro

2. Installed from an earlier ISO, probably one of the Beta images and
then dist-upgraded through till now.

3. I'm grepping now "grep -r set-log-level /"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  Continuous messages from systemd: dm disk appears twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: Continuous messages from systemd: dm disk appears twice

[Matt Schulte]

3. Grep was hanging up on some device files so...

root@ICTM1612S02H2:/# find / -xdev -type f -print0 |xargs -0 grep -H 
"set-log-level"
Binary file /usr/bin/systemd-analyze matches
/usr/share/bash-completion/completions/systemd-analyze:
[LOG_LEVEL]='set-log-level'
/usr/share/apport/symptoms/_audio_data.py:
command_output(['pacmd','set-log-level','4'])
/usr/share/apport/symptoms/_audio_data.py:
command_output(['pacmd','set-log-level','1'])
/usr/share/zsh/vendor-completions/_systemd-analyze:_systemd_analyze_set-log-level()
 {
/usr/share/zsh/vendor-completions/_systemd-analyze:'set-log-level:Set 
systemd log threshold'


4. What kind of system is this...It is a Dell PowerEdge R730, baremetal non-VM 
system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  Continuous messages from systemd: dm disk appears twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: debug messages are enabled

[Matt Schulte]

I have installed a new system from the server CD.  I chose Expert mode
and selected a few special options but nothing too drastic (like setting
up my NTP server and my internal mirror repository).

It does NOT seem to have these messages enabled.  Maybe there was
something funky in the particular image that I used previously?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  debug messages are enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: debug messages are enabled

[Matt Schulte]

I may have spoken too soon, I am seeing them again.

Is there any instance in which I would see these messages under normal
circumstances?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  debug messages are enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Nothing for the system is on iscsi.  They are just extra volumes that I
use for generating block or filesystem IO to our storage.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: Continuous messages from systemd: dm disk appears twice

[Matt Schulte]

I have not touched /etc/systemd/system.conf.  Looking at that file
everything is commented out so I assume defaults.

I don't see anything that says /etc/systemd/system.conf.d...I see
/etc/systemd/system/ but I haven't touched anything in there.

I don't knowingly have a call to systemd-analyze anywhere.  I can grep
my whole system for it if you like.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  Continuous messages from systemd: dm disk appears twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: debug messages are enabled

[Matt Schulte]

I am not sure exactly when they start to appear.

The configuration of NTP and the internal mirror and stuff is done
inside of the installer from the "expert" option on the CD.

Then when it is installed and up I add a few more packages from the
repos.

I am not certain exactly when these start to appear or if they are there
the whole time.   They may only start to appear when I begin testing
failovers with multipath to my storage.

I guess tomorrow I can download the released version of the server cd
and perform the same install and pay attention to exactly when I start
to see these messages.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  debug messages are enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1565969] Re: Udev rule causes automatic incorrect unmount of dm device

[Matt Schulte]

I have run for a bit now and have not seen anymore erroneous unmounts.
I'll call this one fixed and verified.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565969

Title:
  Udev rule causes automatic incorrect unmount of dm device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: Continuous messages from systemd: dm disk appears twice

[Matt Schulte]

Ok, then how can I turn it off?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  Continuous messages from systemd: dm disk appears twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570093] [NEW] multipath-tools update introduced syslog messages about partx

[Matt Schulte]

Public bug reported:

During a path loss event, the syslog is showing these messages where
prior to the recent upgrade to multipath-tools I didn't see anything
like this.  To me this seems like either a problem or it seems like a
print message that should go into a different log file.

Apr 13 11:21:00 ICTM1618S01H4 systemd-udevd[14861]: Process '/usr/bin/partx -d 
--nr 1-1024 /dev/sdam' failed with exit code 1.
...
Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get udev uid: Invalid 
argument
Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sysfs uid: 
Invalid argument
Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sgio uid: No such 
file or directory

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: multipath-tools 0.5.0+git1.656f8865-5ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Wed Apr 13 15:29:36 2016
SourcePackage: multipath-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: multipath-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570093

Title:
  multipath-tools update introduced syslog messages about partx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

In the above, the two NICs used for iSCSI traffic are the enp130s0 and
the enp4s0f0.

In case you were wondering I have another server running ipv4 and it
also hangs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Here is the requested syslog.

Reboot happens after:

Apr 14 09:49:42 ICTM1612S02H1 root: MDS: Rebooting Now

** Attachment added: "requested syslog"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4636878/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: Continuous messages from systemd: dm disk appears twice

[Matt Schulte]

I'm not suggesting that you remove it, but I don't know how it got set
and I am not intentionally setting debug level logging.  Is it possible
that the bug is not that this output exists but instead that the
debugging is turned on?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  Continuous messages from systemd: dm disk appears twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

root@ICTM1612S02H1:/etc/network# cat 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

auto enp130s0
iface enp130s0 inet6 static
address fe80::192:12:21:115
netmask 64
mtu 9000

auto enp4s0f0
iface enp4s0f0 inet6 static
address fe80::192:12:22:115
netmask 64
mtu 9000

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx

[Matt Schulte]

I can confirm that the messages seem to be cleaned up with your fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570093

Title:
  multipath-tools update introduced syslog messages about partx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: debug messages are enabled

[Matt Schulte]

FYI, this behavior persists with the released version of 16.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  debug messages are enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

rc_micha: Your volumes aren't mounted, but the iscsi sessions are logged
in?  If you log out of your iscsi sessions does it shutdown clean?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx

[Matt Schulte]

Do I have to rebuild the package with this debdiff before it can be
accepted?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570093

Title:
  multipath-tools update introduced syslog messages about partx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1615694] Re: [860730] Host experiencing constant session termination and recreation while using jumbo frames

[Matt Schulte]

We're still hoping for a resolution on this one.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615694

Title:
  [860730] Host experiencing constant session termination and recreation
  while using jumbo frames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1615694/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: debug messages are enabled

[Matt Schulte]

Still looking for a resolution to this one.

** Changed in: ubuntu
   Status: Expired => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  debug messages are enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1636862] Re: Shutdown hangs with active iscsi sessions

[Matt Schulte]

Any movement here?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636862

Title:
  Shutdown hangs with active iscsi sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Any idea on this one folks?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1636862] Re: Shutdown hangs with active iscsi sessions

[Matt Schulte]

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

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).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636862

Title:
  Shutdown hangs with active iscsi sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Didn't take as long as I thought.  Installed the most recent build of
Zesty (zesty-server-amd64.iso 2017-02-22 06:54676M).

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).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

It is possible to test without multipath, this will take some time as I
no longer have anything with 16.04 installed.  For fun I may go ahead
and try with 17.04 so we can figure out if it still exists then we'll
kind of kill two birds with one stone.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

iSCSI disks are not the root/boot disks.

Multipath IS in use.  Hence the /dev/mapper at the beginning of the disk
names.

Yes I have tried 16.10, it is still present and I have another bug for
that release.  https://bugs.launchpad.net/bugs/1636862

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

There is clearly something wrong here.

FWIW This issue did not exist in 14.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

** Changed in: systemd (Ubuntu)
   Status: Expired => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

For completeness, I upgraded to 16.04.1, the issue is still present.

I upgraded to the latest xenial-updates packages as of 10/24/16 and the
issue is still present.

I then re-installed with 16.10 and the issue is still present.  I guess
I'll open a new bug for 16.10 and refer back to this one.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

If this is still a problem, what do we do now?  Do I just keep testing
with new releases and file new bugs?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

New bug for 16.10:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636862

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1636862] [NEW] Shutdown hangs with active iscsi sessions

[Matt Schulte]

Public bug reported:

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

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636862

Title:
  Shutdown hangs with active iscsi sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1615694] Re: [860730] Host experiencing constant session termination and recreation while using jumbo frames

[Matt Schulte]

Sure, we can give Debian a shot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615694

Title:
  [860730] Host experiencing constant session termination and recreation
  while using jumbo frames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1615694/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1615694] Re: [860730] Host experiencing constant session termination and recreation while using jumbo frames

[Matt Schulte]

Wait I'm confused, build what in a PPA?  Didn't you just want us to run
Debian and test what the version of open-iscsi it comes with?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615694

Title:
  [860730] Host experiencing constant session termination and recreation
  while using jumbo frames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1615694/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

I can confirm that the daily 17.10 build does not exhibit the problem.

Interestingly, the first time we tried we forgot to stop running IO to
our iSCSI volumes and it _looked_ like we reproduced the problem, then
the IOs timed out and our application stopped and we were able to
complete the reboot.

The next time we retried and correctly stopped our application before
shutting down and had no issue.  Whatever it is, is fixed in 17.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

I have node.session.timeo.replacement_timeout = 20, which seems
completely reasonable in my book.

We have already established that this occurs without multipath even
enabled, thus it is not a multipath settings problem.

Also I have no containers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

My test configuration has long since been re-tasked.  I will eventually
be able to come back and test as you ask, but it may take a few weeks.
If anyone else on the bug has their systems up and available, please
test and reply.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

As I said I don't have one up right now, but Comment 3 above has my
interfaces for one of the recreates.

Nothing bothered me in any way.  I wanted to make sure that you knew
that I wasn't one guy who was looking to fix his one system, that's all.

You said "Usually those type of "partnership" product
enablements/fixes"...what do you mean by that?  Is there some avenue
that I could be pursuing to get my bugs addressed sooner?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Please let me explain who I am and what we do to possibly shed some
light on this.

I am an Interoperability engineer at NetApp.  We test our storage
products with many popular operating systems, adapters, protocols and
switches, in varying combinations.

We test software initiator iscsi continuously (on other distros) with exactly 
the same configuration as I have described above and have never seen this 
behavior.  Indeed whatever the problem is seems fixed in 
Ubuntu upstream as I indicated above.  This is also new behavior introduced 
between 14.04 and 16.04 because it did not occur in older versions.

The purpose of me asking to get this issue resolved is not to fix MY
system, it is to fix it for my customers' systems.  We will not post
support for Ubuntu 16.04 (iscsi) without resolving this issue so that we
don't put our customers in the same position.

With all that said, I do not currently have a configuration available or
setup to reproduce this problem.  If it is required, I can add it to the
queue.  When it is up and running, it reproduces every single time.

Other folks on the thread may actually have it up and running right now
and be able to test the immediate fail before I get to it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Excellent, thank you for the details.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

RE: [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

That's awesome sir, thank you for your diligence.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

I apologize for my ignorance, but now that tall these check ins have
occurred, how do I know when an installable package has been built and
is available in the various repos?

And thank you @inaddy for the diligence getting this one resolved.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

RE: [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

Thanks, and will notifications appear here in the bug during these
stages?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569930] Re: debug messages are enabled

[Matt Schulte]

Ok, I am officially giving up on this one, some one go ahead and close
this out please.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569930

Title:
  debug messages are enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1569930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870146] [NEW] Unable to successfully boot from SAN with multipath SAS volume

[Matt Schulte]

Public bug reported:

I work at NetApp and we have a storage array that has dual SAS
controllers that present multiple paths to a single volume.  We usually
are able to boot from SAN using SAS and utilize multipath on the root
volume.  I have tried everything I can think of and don't get this fully
working.  Here's what I have tried:

1. Installed to a single path (sda) and booted then tried to add the two paths 
to root into multipath.
   a. Followed 
https://help.ubuntu.com/lts/serverguide/multipath-setting-up-dm-multipath.html 
"Setting Up DM-Multipath"  Could not get multipath to manage the paths.
   b. Even tried the instructions from RedHat: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/dm_multipath/move_root_to_multipath
 Manually adding the paths to multipath and then rebuilding the initrd, still 
no dice.

2. Reinstall.  After many struggles I am able to install using the boot 
parameter: install disk-detect/multipath/enable=true
   a. Install completes but the tools are unable to write a boot loader to the 
multipath disk.
   b. Tried booting into a rescue disk to write bootloader and still 
unsuccessful.

Should Ubuntu support boot from SAN using a multipath volume on the SAS
protocol (Broadcom 12G HBAs)?

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870146

Title:
  Unable to successfully boot from SAN with multipath SAS volume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1870146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870146] Re: Unable to successfully boot from SAN with multipath SAS volume

[Matt Schulte]

This has all been testing with Ubuntu 20.04.  When I did have it install
to a single path, I updated everything to the latest (even tried the
proposed stuff) up to 3/30/2020.

When I switched tactics and tried to reinstall I was using an ISO from a
couple weeks ago.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870146

Title:
  Unable to successfully boot from SAN with multipath SAS volume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1870146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870146] Re: Unable to successfully boot from SAN with multipath SAS volume

[Matt Schulte]

At this point I have to assume that booting form SAN using a SAS
multipath device is not compatible with Ubuntu 20.04 and will advise
against its attempted use.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870146

Title:
  Unable to successfully boot from SAN with multipath SAS volume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1870146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870146] Re: Unable to successfully boot from SAN with multipath SAS volume

[Matt Schulte]

Anybody have anything to add here?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870146

Title:
  Unable to successfully boot from SAN with multipath SAS volume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1870146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867366] Re: hostnqn fails to automatically generate after installing nvme-cli

[Matt Schulte]

Rafael, would it be wrong to simply take any existing files and save
them with an .bak extension?  That way if the user really wanted their
old ID they could go get it back?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867366

Title:
  hostnqn fails to automatically generate after installing nvme-cli

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1867366/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867366] Re: hostnqn fails to automatically generate after installing nvme-cli

[Matt Schulte]

Yeah, makes sense.  I would say to try to follow the iscsi iqn behavior,
good idea!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867366

Title:
  hostnqn fails to automatically generate after installing nvme-cli

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1867366/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874270] Re: NVMe/FC connections fail to reestablish after controller is reset

[Matt Schulte]

** Changed in: nvme-cli (Ubuntu)
   Status: Expired => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874270

Title:
  NVMe/FC connections fail to reestablish after controller is reset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1874270/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs