Hi Tim,
Sorry, this has been closed as unreproducible on the LTC side, and not
reflected here.
Marking this bug as Invalid.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tim,
This looks like the same deal w/ the other bug today; closed as unreproducible,
which was not reflected here.
I'll pass this on to the bug bridge team.
This has been posted as an internal (hm.) comment:
> This issue is not getting re-created with recent ubuntu build.
** Changed in: linux
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497966
Title:
ISST-KVM:R3-0:Firestone:Ubuntu14043:beng2:Cannot reach network with
Thanks; asked the test team to verify the installation w/ apt-
setup/proposed=true, and will update once verified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501015
Title:
ISST-LTE: Multipath
Thanks!
The udeb in -proposed contains the ql2500_fw.bin file.
Verified the file and the build log.
Setting verification-done.
@ scsi-firmware_1.127.20_all.udeb
$ wget
https://launchpad.net/ubuntu/+archive/primary/+files/scsi-firmware_1.127.20_all.udeb
<...>
$ ar x
Hi @mathieu-tl,
Mathieu Trudel-Lapierre (mathieu-tl) on 2016-02-01
> description: updated
> Changed in multipath-tools (Ubuntu Trusty):
> status: New → Incomplete
Can you clarify the status 'incomplete' for this bug?
Is that indeed an information request for submitter (where, please) or
Hi @mathieu-tl,
Mathieu Trudel-Lapierre (mathieu-tl) on 2016-02-01
> description: updated
> Changed in multipath-tools (Ubuntu Trusty):
> status: New → Incomplete
Can you clarify the status 'incomplete' for this bug?
Is that indeed an information request for submitter (where, please) or
This may be similar to LP 1523637.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533587
Title:
Ubuntu 14.04.04 installer does not list Prep Boot in Partition
Settings
To manage notifications
Verified on 14.04.
Marking verification-done.
As mentioned in the description test-case, the issue is hard to reproduce.
Trying to force it to happen, I modified the updated package
local-premount/multipath
script to remove/rescan the SCSI devices in the background right before the
udevadm
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503286
Title:
ISST-LTE: Boot of Ubuntu15.10 lpar fails: "mounting /dev/sdn2 on
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1503286
Title:
ISST-LTE: Boot of Ubuntu15.10 lpar
Verified on 14.04.
Marking verification-done.
As mentioned in the description test-case, the issue is hard to reproduce.
Trying to force it to happen, I modified the updated package
local-premount/multipath
script to remove/rescan the SCSI devices in the background right before the
udevadm
Hi @stu-g,
Thanks for your report.
I think the problem you're experiencing (handled in LP 1538775) is one we've
been discussing/trying to get around for some time now.
Since scsi_wait_scan was removed, there's no way to really wait /on the SCSI
scan/.
For that objective, udevadm settle won't
This is working correctly.
Marking as verification-done.
After partitioning with parted, there's only one device node for the
partition (with the -part disk-partition separator).
There's /still/ some messages in parted mentioning it could not find the
device, but the partitions are created
This is working correctly.
Marking as verification-done.
After partitioning with parted, there's only one device node for the
partition (with the -part disk-partition separator).
There's /still/ some messages in parted mentioning it could not find the
device, but the partitions are created
This is working correctly w/ kpartx.
One instance it seems to be still generating symlinks/nodes intermixed is when
using parted.
However, during reboot and post-boot kpartx invocation, it is pretty consistent
w/ only nodes.
So, this seems correct with regards to the code in multipath-tools.
This is working correctly w/ kpartx.
One instance it seems to be still generating symlinks/nodes intermixed is when
using parted.
However, during reboot and post-boot kpartx invocation, it is pretty consistent
w/ only nodes.
So, this seems correct with regards to the code in multipath-tools.
I verified this works correctly on 2 LPARs, including the original LPAR from
the bug report. (Thanks, Michail)
Marking as verification-done.
Installed the version from -proposed:
root@pinelp2:~# dpkg -l | grep 0.4.9-3ubuntu7.8
ii kpartx
I verified this works correctly on 2 LPARs, including the original LPAR from
the bug report. (Thanks, Michail)
Marking as verification-done.
Installed the version from -proposed:
root@pinelp2:~# dpkg -l | grep 0.4.9-3ubuntu7.8
ii kpartx
Hi,
Given the conversation/explanation on this bug (1: problem is lack of
SCSI wait scan, and 2: this bug targets to remove the error message),
and my additional comments on bug 1526984 comment #18 (summary: the SCSI
wait scan problem is not supposed to be fixed with either udevadm settle
/
Hi,
Given the conversation/explanation on this bug (1: problem is lack of
SCSI wait scan, and 2: this bug targets to remove the error message),
and my additional comments on bug 1526984 comment #18 (summary: the SCSI
wait scan problem is not supposed to be fixed with either udevadm settle
/
Hi @stu-g,
Thanks for your report.
I think the problem you're experiencing (handled in LP 1538775) is one we've
been discussing/trying to get around for some time now.
Since scsi_wait_scan was removed, there's no way to really wait /on the SCSI
scan/.
For that objective, udevadm settle won't
Hi @mathieu-tl,
Here is the patch for Xenial.
Differences from the patch for Trusty:
1) install udev rule with priority 56, so it's run after 55-scsi-sg3_id; this
way the paths actually have scsi id udev attributes defined by the time
'multipath -c' runs, and now it works fine (fixes the issue
Hi @mathieu-tl,
Here is the patch for Xenial.
Differences from the patch for Trusty:
1) install udev rule with priority 56, so it's run after 55-scsi-sg3_id; this
way the paths actually have scsi id udev attributes defined by the time
'multipath -c' runs, and now it works fine (fixes the issue
The snippets for IBM XIV are present in the source.
# head -n1 debian/changelog
multipath-tools (0.4.9-3ubuntu7.8) trusty; urgency=medium
# sed -n '/IBM XIV/,/}/ p' libmultipath/hwtable.c
/* IBM XIV Storage System */
.vendor= "IBM",
Marking as verification-done.
Details:
---
qemu-kvm guest w/ rootfs on multipath
# mount | grep ' / '
/dev/mapper/mauricfo4--vg-root on / type ext4 (rw,errors=remount-ro)
# lvm pvdisplay | grep Name
PV Name /dev/mapper/mpath0-part3
Marking as verification-done.
Details:
---
qemu-kvm guest w/ rootfs on multipath
# mount | grep ' / '
/dev/mapper/mauricfo4--vg-root on / type ext4 (rw,errors=remount-ro)
# lvm pvdisplay | grep Name
PV Name /dev/mapper/mpath0-part3
Testing w/ pure multipath setup (non-LVM).
Boots successfully, w/ no prompts.
# mount | grep ' / '
/dev/mapper/mpath0-part2 on / type ext4 (rw,errors=remount-ro)
# multipath -l
mpath0 (0QEMUQEMU HARDDISK trustyroot) dm-0 QEMU,QEMU HARDDISK
size=32G features='0' hwhandler='0' wp=rw
Testing w/ pure multipath setup (non-LVM).
Boots successfully, w/ no prompts.
# mount | grep ' / '
/dev/mapper/mpath0-part2 on / type ext4 (rw,errors=remount-ro)
# multipath -l
mpath0 (0QEMUQEMU HARDDISK trustyroot) dm-0 QEMU,QEMU HARDDISK
size=32G features='0' hwhandler='0' wp=rw
The snippets for IBM XIV are present in the source.
# head -n1 debian/changelog
multipath-tools (0.4.9-3ubuntu7.8) trusty; urgency=medium
# sed -n '/IBM XIV/,/}/ p' libmultipath/hwtable.c
/* IBM XIV Storage System */
.vendor= "IBM",
Hi @mathew-hodson,
In case it helps,
I believe this bug is likely to be assigned to @mathieu-tl.
We've been working on these sort of problems, and talked about a tentative
14.04.4 milestone.
Thanks!
PS. Deleted previous attachment/patch version.
** Patch removed: "Patch for booting with LVM
Hi @mathew-hodson,
In case it helps,
I believe this bug is likely to be assigned to @mathieu-tl.
We've been working on these sort of problems, and talked about a tentative
14.04.4 milestone.
Thanks!
PS. Deleted previous attachment/patch version.
** Patch removed: "Patch for booting with LVM
Hi @mathieu-tl,
Friendly asking. The fix has been in -proposed for 7+ days now. Is it
making -updates before GA? :)
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487365
Title:
@mathieu-tl
Thank you very much ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487365
Title:
Ubuntu14.04 .3 RAID installation fails on firestone
To manage notifications about this bug go to:
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401
Title:
ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
disk drive
Hi @mathieu-tl,
> This patch has been verified to resolve this problem (thanks Kevin),
and another one which is being mirrored.
The other bug's mirroring has been cancelled. It's been identified as
too similar to this one.
FYI, in case you may see it elsewhere, hope this description may save
Public bug reported:
During a Xenial installation, the multipath devices from an IBM IPR
controller were not discovered, as the block devices lacked the
SCSI_IDENT_* udev properties.
The fix was to simply reload udev rules and re-add the devices w/
update-dev; and the devices were correctly
Hi @mathieu-tl,
Can you check this bug/patch, please?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549456
Title:
multipath discovery failed during install due to missing udev
properties
** Patch added: "mdadm_3_mpathmdadm.debdiff"
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1549506/+attachment/4580433/+files/mdadm_3_mpathmdadm.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Similarly to bug 1549504 (for LVM), but this one with LVM on top of md
arrays.
During a Xenial installation, some of the multipath devices were not
discovered, as individual paths were locked by MD arrays.
The fix is to deactivate MD arrays before multipath discovery (in
Hi @mathieu-tl,
Can you check this bug/patches, please?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549504
Title:
multipath discovery failed during install due to LVM volumes locking
Hi @mathieu-tl,
Can you check this bug/patches, please?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549506
Title:
multipath discovery failed during install due to md arrays locking
Hi @mathieu-tl
Unfortunately the patch that made the package is that w/out the NVMe regex
(comment #2).
I see that bugproxy reposted the old patch.. heck (no idea why). Apologies if
that caused the confusion.
Can you please adjust the grep regex for that in comment #2?
Thanks!
--
You
One slight change to the patch.
It worked for sd/vd disks, but not for NVMe :)
Just fixed the regex and tested on a system w/ 2 NVMe disks.
Change to this line only:
grep -o '/dev/\([sv]d[a-z]\+\|nvme[0-9]\+n[0-9]\+p\)'
** Attachment removed: "grub-installer_multi-prep.debdiff"
Public bug reported:
During a Xenial installation, some of the multipath devices were not
discovered, as individual paths were locked by active LVM volumes.
The fix is to deactivate LVM volumes before multipath discovery (in hw-
detect), and activate multipath partitions during partman/init.d
** Patch added: "partman-multipath_2_mpathlvm.debdiff"
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1549504/+attachment/4580431/+files/partman-multipath_2_mpathlvm.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The patch has been applied upstream [1] in a slight different form -- the
debdiff attached here is the backport for Trusty.
The difference is just MAJOR()/MINOR() vs. major()/minor().
[1] http://git.opensvc.com/gitweb.cgi?p=multipath-
The patch has been applied upstream [1] in a slight different form -- the
debdiff attached here is the backport for Trusty.
The difference is just MAJOR()/MINOR() vs. major()/minor().
[1] http://git.opensvc.com/gitweb.cgi?p=multipath-
The test team verified the package in -proposed works OK.
Setting verification-done.
> Chanh H. Nguyen 2016-01-19 14:43:28 BRST
>> Bug Review: waiting on reporter to verify packages w/ fix from the -proposed
>> repository.
>
> Yes, it works fine when I use the "apt-setup/proposed=true" at the
I verified this on Trusty w/ apt-setup/proposed=true.
The installation finishes fine (no errors on grub-installer), and the system
boots fine.
Marking verification-done.
Installation instructions for Software RAID have been documented in the
SoftwareRAID [1] wiki page, and linked from the
This is verified OK on Trusty:
# lsb_release -c
Codename: trusty
# dpkg -s multipath-tools | grep ^Version
Version: 0.4.9-3ubuntu7.11
# ls -1 /dev/nvme*
/dev/nvme0
/dev/nvme0n1
/dev/nvme0n1p1
/dev/nvme0n1p2
/dev/nvme0n1p3
# multipath -v3 /dev/nvme0n1
Apr 07 13:25:25 | nvme0n1: device
I believe there are several other cases, specially among test teams and
some cloud deployments, where they download an ISO and use it as a
network install mirror, in order to save network bandwidth / install
time.
However, they need to get the vmlinux/initrd from
ports.ubuntu.com/netboot (with
About more testing..
If that helps, at least one test team here at IBM will perform multipath
testing on 16.04 from Final Beta Freeze (March 24, currently) throughout
release/GA on April 21.
They drove lots of the multipath bugs that I've worked on and bugged
@mathieu-tl with since 15.04 :)
About more testing..
If that helps, at least one test team here at IBM will perform multipath
testing on 16.04 from Final Beta Freeze (March 24, currently) throughout
release/GA on April 21.
They drove lots of the multipath bugs that I've worked on and bugged
@mathieu-tl with since 15.04 :)
Public bug reported:
Noticed this while installing debug symbols for systemd:
# apt install systemd-dbg
...
Unpacking udev (229-3ubuntu1) over (229-2ubuntu1) ...
...
Setting up udev (229-3ubuntu1) ...
addgroup: The group `input' already exists as a system group. Exiting.
Hi @toreanderson,
The not relevant statement is not at you :) just explaining why I didn't
verify on vivid.
I've seen some reports that this functionality is no longer working on
Trusty too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi @toreanderson,
The not relevant statement is not at you :) just explaining why I didn't
verify on vivid.
I've seen some reports that this functionality is no longer working on
Trusty too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401
Title:
ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation:
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1540401
Title:
ISST-LTE: Ubuntu14.04.4 lpar fails to
The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.
--
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/1435706
Title:
DevLossTO, FastIoFailTO
The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.
--
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/1386637
Title:
multipath shows non-mpath
The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435706
Title:
DevLossTO, FastIoFailTO settings do not match
The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468897
Title:
multipath creates binding for Removable(USB) drives
The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386637
Title:
multipath shows non-mpath disks as being multipath
The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.
--
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/1468897
Title:
multipath creates binding
@taco-screen-team
I'd suggest for @cyphermox (formerly @mathieu-tl) to look at this one.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561103
Title:
Multipath assigned user_friendly_names
@taco-screen-team
I'd suggest for @cyphermox (formerly @mathieu-tl) to look at this one.
Thanks
--
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/1561103
Title:
Multipath
(there's a comment with more detailed description coming via the
bridge..)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565817
Title:
multipath: LVM physical volumes on individual paths
To
Hi @raharper and @cyphermox,
There's been 2 regressions identified by testing.
Please see the debdiff in LP bug 1565817, which addresses them.
May you please review/consider it for an upload?
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@taco-screen-team please assign to @cyphermox. thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565817
Title:
multipath: LVM physical volumes on individual paths
To manage notifications
Hi @raharper,
Thanks for the review.
> --- Comment From raharper 2016-04-04 23:25:18 UTC---
> Hello,
>
> Thanks for sending the debdiff. Have you filed bugs against debian for
> these issues? ie are they present in debian unstable at this point or are we
> bringing in known fixes from
@mathieu-tl,
Do you plan to upload the remaining patch for mdadm as well?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549506
Title:
multipath discovery failed during install due to md
@mathieu-tl,
Do you plan to upload the remaining patch for partman-multipath as well?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549504
Title:
multipath discovery failed during install
Public bug reported:
Hi Canonical,
This a "duplicate" of LP #1580557 comment #1 (yes, a comment).
(It seems there was a problem in the bug bridge and it merged 2 bugs.)
This is about including these 2 upstream commits for the lpfc driver:
Mauricio Faria De Oliveira 2016-05-11 08:37
Hi,
Apologies for the confusion w/ the bug bridge; it has been reported.
LP 1580557 and LP 1580560 are the same bug (previously marked as a dup,
but removed later).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1572624 ***
https://bugs.launchpad.net/bugs/1572624
Hi,
Apologies for the confusion w/ the bug bridge; it has been reported.
LP 1580557 and LP 1580560 are the same bug (previously marked as a dup,
but removed later).
It seems the invalidation of this one
Marking as verification done.
The commit is present on the git tag for the -proposed kernel [1].
It was not possible to re-verify this kernel package on the original equipment
that reproduced the problem,
but the commit itself was verified earlier on it to resolve it (documented in
comment
Hi Christian,
Thanks for handling it to xenial-updates.
BTW, that point about the package to make the point release ISO is so
that people who use the ISO as package repository (which happens in some
scenarios like xCAT clusters), and not always get more updates from the
internet, can get it.
Christian,
Thanks for handling this.
> But the more that are affected the more I think then general solution
in lightdm would be the right thing to do.
Yes, that's my interpretation too -- and it was my impression from the
beginning, with your report/analysis, as I couldn't find anything we
Christian,
For your consideration...
Since this patch is mainly targeted at first-time installations of libvirt (so
that the uid assignment can occur), it would be great if it can make 16.04.2
now that the date slipped 2 weeks (per the public release schedule), if at all
possible... so that
Hi Christian,
Here's the patch for libvirt in Xenial.
It's the very minimal changes required from Zesty/Debian in order to set the
UID (and document the change in the NEWS file).
I didn't backport the debconf warning stuff as it's not essentially required.
Hopefully this is simple/conservative
Verification steps with just attached patch.
Test 1) new user, uid available
Result) libvirt-qemu uid is set to 64055
# id libvirt-qemu
id: ‘libvirt-qemu’: no such user
# getent passwd 64055
#
# dpkg -i
Christian,
Alright!
I'll provide the up-to-date backport for libvirt in Xenial and the SRU template.
Per Colin's comment #21 it's not required to SRU base-passwd:
> [snip] you should definitely not waste time SRUing base-passwd [snip]
Thanks.
--
You received this bug notification because you
Okay, great! 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/1637601
Title:
UbuntuKVM: migration using NFS mount fails #190
To manage notifications about this bug go to:
Okay, thanks again for all you (excellent) support on all this,
Christian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637601
Title:
UbuntuKVM: migration using NFS mount fails #190
To manage
> 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'.
Right.
This is just a request for adding the patch which fixes a potential problem in
an applied patch.
Changing
The patch in the kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2017-March/082822.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669153
Title:
Add Use-After-Free Patch
Thanks for marking this bug as verified.
It looks good -- I've checked the patch is there, and change is trivial,
but couldn't get a response from the test team in time. Sorry for that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@taco-screen-team, may @cyphermox check this one? we've worked on this
area/kind of bugs in the past.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615650
Title:
Guided Partitioning does not list
@taco-screen-team
Can this bug be assigned to @adconrad (commented earlier on this bug) or
@cyphermox (previous installer fixes in this area)?
Patch attached.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sigh.
The bug bridge ate the comment delimiters.
I'll paste the comments in order here in LP, and chop a bit.
Hopefully that will allow humans to understand this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Comment:
The problem is due to a configuration problem in the NFSv4 server and/or
clients.
Probably related to the NFSv4 ID <-> Name Mapping (idmap).
Thus, this is not an I/O-related problem.
The solution/requirement is to make sure that the libvirt-qemu user has
the same UID/GID on all
Problem:
We setup 2 Ubuntu KVM host with the same mount point and try to migration the
guest between 2 HOST. The migration is success, the guest appear on other Host
after the migration but it shows some I/O error on the guest.
<...>
On the first host, run this
root@micro:~# virsh migrate
Comment:
Hi Canonical,
@taco-screen-team
The attached patches are for Zesty, Xenial, and Debian sid (which I plan
to submit if the UID/GID allocation request is granted).
afaik @cjwatson is the maintainer of base-passwd on Debian, and could
review/grant/deny the allocation request.
Per Ubuntu
Comment:
The reservation of an UID/GID in Debian/Ubuntu follows an allocation process
governed by Debian.
I have submitted an allocation request, and will prepare the patches for
libvirt-qemu in Debian and Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Comment:
Hi Mauricio,
Yes, after applied this patch, the migration is working fine without any
IO error.
I am able to migrate between 2 Host (Tiny & Micro) using the NFS mount
method without any IO issue.
root@micro:~# id libvirt-qemu
uid=64055(libvirt-qemu) gid=117(kvm)
Comment:
Hi Chanh,
Can you please test the libvirt-bin & libvirt0 packages?
http://ausgsa.ibm.com/~mauricfo/public/bugs/bz145069/v2/
Please confirm if they resolve the issue.
Thanks!
Details
---
The test packages assume that the UID & GID 64055 will be allocated by
Debian, and user this
this on Debian and Ubuntu, right?
For reference, this is the e-mail sent to Debian base-passwd:
Forwarded Message
Subject: request uid and gid allocation for libvirt-qemu
Date: Tue, 25 Oct 2016 09:27:00 -0200
From: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com>
To: ba
Hi @paelzer,
> I meant a Debian bug against base-passwd to begin with not a libvirt bug.
> I think the Mail you have written is a good start, yet IMHO a related bug
> can't hurt t track and make them more aware.
Ah, ok. Yes, you're right. That is BTS #843881 [1].
> Yes it is primarily
Hi Christian Ehrhardt,
Attaching PATCH v2 for Xenial.
It only checks/sets the UID for libvirt-qemu user; no other actions/changes
performed.
** Patch added: "xenial_libvirt_uidgid_v2.debdiff"
301 - 400 of 1696 matches
Mail list logo
