This bug was fixed in the package multipath-tools - 0.5.0-7ubuntu1
---
multipath-tools (0.5.0-7ubuntu1) wily; urgency=medium
* Merge from debian unstable, remaining changes: (LP: #1455482)
- control:
* Bump debhelper dependency to install udev rules to
This bug was fixed in the package multipath-tools - 0.5.0-7ubuntu1
---
multipath-tools (0.5.0-7ubuntu1) wily; urgency=medium
* Merge from debian unstable, remaining changes: (LP: #1455482)
- control:
* Bump debhelper dependency to install udev rules to
Still working on it. With sg3-utils adapted to also ship a sg3-udeb
package for use by the installer (which multipath-udeb can depend on so
it's available to the installer), things appear to work more or less
properly. To be able to ship this we still need the dm-service-time
module available in
Still working on it. With sg3-utils adapted to also ship a sg3-udeb
package for use by the installer (which multipath-udeb can depend on so
it's available to the installer), things appear to work more or less
properly. To be able to ship this we still need the dm-service-time
module available in
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade multipath-tools to upstream
To manage notifications about this bug go to:
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade multipath-tools to upstream
To manage
I pulled both multipath-tools directly from Debian and did a merge of
multipath-tools 0.5.0 with Ubuntu changes; both seem to currently be
unable to notice that QEMU harddrives should be multipathed. I'm
investigating the situation.
--
You received this bug notification because you are a member
I pulled both multipath-tools directly from Debian and did a merge of
multipath-tools 0.5.0 with Ubuntu changes; both seem to currently be
unable to notice that QEMU harddrives should be multipathed. I'm
investigating the situation.
--
You received this bug notification because you are a member
@mathieu-tl
unable to notice that QEMU harddrives should be multipathed. I'm
This brings 2 things to mind:
1) the property whitelist support (see one or two of those BTS bugs, for the
uid / udev ID_SERIAL change -- one is for sg3-utils)
2) (don't think this is the case) if you're not using
@mathieu-tl
unable to notice that QEMU harddrives should be multipathed. I'm
This brings 2 things to mind:
1) the property whitelist support (see one or two of those BTS bugs, for the
uid / udev ID_SERIAL change -- one is for sg3-utils)
2) (don't think this is the case) if you're not using
Well, that change was made for a good reason; multipath now no longer
depends on scsi_id to be able to pick drives to use to multipath, and we
can explicitly whitelist (or use blacklist_exclusions) devices or re-
enable ID_SERIAL by modifying multipath.conf. Is this affecting other
drives than the
Well, that change was made for a good reason; multipath now no longer
depends on scsi_id to be able to pick drives to use to multipath, and we
can explicitly whitelist (or use blacklist_exclusions) devices or re-
enable ID_SERIAL by modifying multipath.conf. Is this affecting other
drives than the
Well, that change was made for a good reason; snip
Is this affecting other drives than the QEMU ones for your use-case?
Agree, good reasons. Yes, the IPR disks show up as SCSI ones.
And if there's no other attributes (say, the SCSI_* udev attributes which
sg3-utils udev rules can set), the IBM
Well, that change was made for a good reason; snip
Is this affecting other drives than the QEMU ones for your use-case?
Agree, good reasons. Yes, the IPR disks show up as SCSI ones.
And if there's no other attributes (say, the SCSI_* udev attributes which
sg3-utils udev rules can set), the IBM
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade multipath-tools to upstream
To manage
Closing the mpath[0-9]/[a-z] discussion..
Just the merge with Debian will do it, as long as Ubuntu drops patch 0002.
Debian returned to mpath[a-z] (dropping patch 0002) a few months after Ubuntu
branched off from 0.4.9-3 for Precise.
This will require changes to the installer packages; the
Closing the mpath[0-9]/[a-z] discussion..
Just the merge with Debian will do it, as long as Ubuntu drops patch 0002.
Debian returned to mpath[a-z] (dropping patch 0002) a few months after Ubuntu
branched off from 0.4.9-3 for Precise.
This will require changes to the installer packages; the
Mathieu,
One of the things where Debian differs from upstream (but not new) is to stick
with mpath[0-9]+ rather than mpath[a-z]+.
This is in patch 0002, iirc.
Can we switch over or (easier) rebase/move it toward the end of the series?
If it's not possible to switch over (we already know where
Mathieu,
One of the things where Debian differs from upstream (but not new) is to stick
with mpath[0-9]+ rather than mpath[a-z]+.
This is in patch 0002, iirc.
Can we switch over or (easier) rebase/move it toward the end of the series?
If it's not possible to switch over (we already know where
Ideal for that would be to convince the Debian maintainers to drop the
patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade
Heheh, alright.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade multipath-tools to upstream
To manage notifications about this bug go to:
Heheh, alright.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade multipath-tools to upstream
To manage notifications about this
Ideal for that would be to convince the Debian maintainers to drop the
patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade multipath-tools to upstream
To manage
The 2 options are drop or rebase.
Regarding drop, the reason to ask Ubuntu is because Debian just
released, and it would break w/ their release contents, which adds more
work in updates/maintainence. AFAIK, Ubuntu releases are more
independent of each other in the updates sense (please correct me
The 2 options are drop or rebase.
Regarding drop, the reason to ask Ubuntu is because Debian just
released, and it would break w/ their release contents, which adds more
work in updates/maintainence. AFAIK, Ubuntu releases are more
independent of each other in the updates sense (please correct me
Hi Steve,
I see the points about upstream/unreleased trunk. I'm not aware of
plans/how the dm/m-t community plans for releases.
Well, Debian 0.5.0 would help to a reasonable extent.
multipath-tools 0.5.0 fixes a number of issues encountered here, and is in a
better position regarding backports.
I went ahead and asked about a timeline for a next multipath-tools
release on the dm-devel mailing list. Timeline was said to be before
summer holidays.
I'll do the multipath-tools merge with Debian so we get 0.5.0, and once
there is a new release we'll see if it can make it into 15.10, if it
I went ahead and asked about a timeline for a next multipath-tools
release on the dm-devel mailing list. Timeline was said to be before
summer holidays.
I'll do the multipath-tools merge with Debian so we get 0.5.0, and once
there is a new release we'll see if it can make it into 15.10, if it
Hi Steve,
I see the points about upstream/unreleased trunk. I'm not aware of
plans/how the dm/m-t community plans for releases.
Well, Debian 0.5.0 would help to a reasonable extent.
multipath-tools 0.5.0 fixes a number of issues encountered here, and is in a
better position regarding backports.
The BTS bugs w/ the fixes I mentioned earlier:
782488
782400
782487
@mathieu-tl I'm not sure which contry the summer holidays relate to,
possibly France? (I guess Christophe lives there?) Would you know?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The BTS bugs w/ the fixes I mentioned earlier:
782488
782400
782487
@mathieu-tl I'm not sure which contry the summer holidays relate to,
possibly France? (I guess Christophe lives there?) Would you know?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server
No idea. I think can operate with the usual procedures: merge now with
0.5.0, and either merge or do an updated package once a new release is
available, provided it happens before Feature Freeze (August 20).
I'll include patches for the above bugs as I merge multipath-tools.
--
You received
No idea. I think can operate with the usual procedures: merge now with
0.5.0, and either merge or do an updated package once a new release is
available, provided it happens before Feature Freeze (August 20).
I'll include patches for the above bugs as I merge multipath-tools.
--
You received
Tracking an upstream trunk that has not been QAed for a release is not
necessarily something we want to do. Do you know if upstream has
another release planned?
Are the issues that are being encountered in testing present with
multipath-tools 0.5.0? Debian has 0.5.0 but Ubuntu is still at
Tracking an upstream trunk that has not been QAed for a release is not
necessarily something we want to do. Do you know if upstream has
another release planned?
Are the issues that are being encountered in testing present with
multipath-tools 0.5.0? Debian has 0.5.0 but Ubuntu is still at
** Package changed: ubuntu = multipath-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade multipath-tools to upstream
To manage notifications about this
** Package changed: ubuntu = multipath-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1455482
Title:
Multipath: upgrade multipath-tools to upstream
To
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
39 matches
Mail list logo
