multipath keep failure after the interface is recovered

Bug #1499622 reported by jay.xu
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
In Progress
High
Unassigned

Bug Description

We encounter a multipath issue on Ubuntu 14.04.2 LTS.

dm state (i.e. failed) cannot be recovered automatically when the interface is back. But path check state (i.e. faulty) can.

In order to describe the issue clearly, the attached slides shows the detail of reproduce steps.
Meanwhile, attachment also includes the output from multipath tool.

P.S. We are writing the IO to the volume through dm device during the interface enable/disable.

Revision history for this message
jay.xu (jay.xu) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1499622

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
jay.xu (jay.xu) wrote :

The issue when I running the command above. Seems that it is blocked by EMC corporate firewall.

stack@openstack:~$ apport-collect 1499622
ERROR: connecting to Launchpad failed: [Errno 1] _ssl.c:510: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
You can reset the credentials by removing the file "/home/stack/.cache/apport/launchpad.credentials"
stack@openstack:~$

By the way, I tried to rest the credentials by removing the file above, still does not work.

Is there any other command I can run and post the log manually?

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
jay.xu (jay.xu) wrote :

Any comment on that?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.3 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc3-unstable/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Changed in linux (Ubuntu):
importance: Medium → High
status: Confirmed → Incomplete
Revision history for this message
jay.xu (jay.xu) wrote :

I did not do any update/upgrade. This issue happens on Ubuntu 14.04.2 LTS. Could you reproduce this issue in Ubuntu 14.04.2 LTS?

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote :

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1499622

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Elisabeth (elisabeth-kemper) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does this issue happen with 14.04.3 or 14.04.4? 14.04.2 is based on the 3.16 kernel, which is no longer supported.

tags: added: kernel-key
removed: kernel-da-key
tags: added: trusty
Revision history for this message
Elisabeth (elisabeth-kemper) wrote : RE: [Bug 1499622] Re: multipath keep failure after the interface is recovered

Hi Joseph,

We had this issue actually with Ubuntu 12.04.5. But
Jay, who originally created the bugreport, reproduced it on 14.04.
@Jay, could you answer the question?

Thanks,
   //Lisa

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Joseph Salisbury
Sent: Thursday, November 12, 2015 4:37 PM
To: Elisabeth Kemper
Subject: [Bug 1499622] Re: multipath keep failure after the interface is recovered

Does this issue happen with 14.04.3 or 14.04.4? 14.04.2 is based on the
3.16 kernel, which is no longer supported.

** Tags removed: kernel-da-key
** Tags added: kernel-key

** Tags added: trusty

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1499622

Title:
  multipath keep failure after the interface is recovered

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We encounter a multipath issue on Ubuntu 14.04.2 LTS.

  dm state (i.e. failed) cannot be recovered automatically when the
  interface is back. But path check state (i.e. faulty) can.

  In order to describe the issue clearly, the attached slides shows the detail of reproduce steps.
  Meanwhile, attachment also includes the output from multipath tool.

  P.S. We are writing the IO to the volume through dm device during the
  interface enable/disable.

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

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

So you are also seeing this with 12.04.5? If that is the case it would be good to see if this issue is already fixed in the mainline kernel, which can be downloaded from:

 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc2+cod1-wily/

tags: added: kernel-da-key
removed: kernel-key
jay.xu (jay.xu)
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
status: Fix Released → In Progress
Revision history for this message
Mark Brown (mstevenbrown) wrote :

What is the current status of the fix for this problem?

Revision history for this message
Elisabeth (elisabeth-kemper) wrote :

Hi,
we got twice a new multipath-tools package fixing the issue but unfortunately
the multipath daemon is crashing with it.
Canonical is still investigating on this issue.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Mark Brown
Sent: Wednesday, January 27, 2016 3:04 PM
To: Elisabeth Kemper
Subject: [Bug 1499622] Re: multipath keep failure after the interface is recovered

What is the current status of the fix for this problem?

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1499622

Title:
  multipath keep failure after the interface is recovered

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We encounter a multipath issue on Ubuntu 14.04.2 LTS.

  dm state (i.e. failed) cannot be recovered automatically when the
  interface is back. But path check state (i.e. faulty) can.

  In order to describe the issue clearly, the attached slides shows the detail of reproduce steps.
  Meanwhile, attachment also includes the output from multipath tool.

  P.S. We are writing the IO to the volume through dm device during the
  interface enable/disable.

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

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.