I picked up a report today on IRC which I wanted to discuss here with
the audience that created the change.
The report was that with 16.04.2 the libvirt user now shows up on e.g.
gdm dropdown when selecting users.
I thought it filters system users, but then --system (=get a low number) and
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.
This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.7
---
libvirt (1.3.1-1ubuntu10.7) xenial; urgency=medium
[ Mauricio Faria de Oliveira ]
* Use a fixed uid/gid for libvirt-qemu user to avoid permission
issues on network filesystems like NFS (backport) (LP:
FYI - I pinged internally again to consider it for the point release as you
requested it.
Quoting you from commend 57 - "Since this patch is mainly targeted at
first-time installations of libvirt (so that the uid assignment can occur)".
But since it is not auto-installed an "apt update" prior
Issue did no more show up on two retries of the test, also what showed up was
totally unrelated to the upload we made.
That said should be safe to migrate now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I found (thank apw) that this triggers an unrelated dep8 test fail which is the
reason it stalled.
Investigating ...
--
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:
Verification was done 17 days ago, I think that should be ok to migrate
right?
Also we have another set of SRU in queue waiting for this to get out of
the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--- Comment From mauri...@br.ibm.com 2017-01-20 08:47 EDT---
Verification done with Xenial. All good!
# lsb_release -d
Description:Ubuntu 16.04.1 LTS
Previous Package:
0) No existing user/uid:
# id libvirt-qemu
id: ?libvirt-qemu?: no such user
# getent passwd
Hello bugproxy, or anyone else affected,
Accepted libvirt into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.3.1-1ubuntu10.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Also affects: base-passwd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: base-passwd (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: libvirt (Ubuntu Xenial)
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
Ok, test succeeded - sponsoring the upload.
It is in the SRU queue now and I pinged the Release Team for you if
there is any chance to slip into 16.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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:
Slightly adapted the versioning, other than that great work IMHO!
I also agree to keep the "LIBVIRT_QEMU_GID=64055 # not used in Xenial." around.
It doesn't hurt and makes it more clear why it is NOT here.
SRU always being extra cautious - Building/Testing from ppa now.
I need to run now, but
Sure, I added that the simplified test is just the user check after fresh
install.
I can only do as fast as possible - not direct effect to the point release by
me.
I can ask a few other people thou to advise on it after I put it into the queue.
And thanks for the paperwork on the SRU - if the
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
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
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
On Tue, Jan 17, 2017 at 8:45 PM, Mauricio Faria de Oliveira <
mauri...@linux.vnet.ibm.com> wrote:
> Per Colin's comment #21 it's not required to SRU base-passwd:
> > [snip] you should definitely not waste time SRUing base-passwd [snip]
>
Glad that you memorized that part better than I did :-)
Ok
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
Hi Mauricio,
this being in zesty due to the merge of latest Debian as planned by Debian
picking up your changes as discussed.
That said, it would be very kind if you did a check if it works for you
as intended.
It does for me, but an ack would be nice
$ id libvirt-qemu
uid=64055(libvirt-qemu)
This bug was fixed in the package libvirt - 2.5.0-3ubuntu1
---
libvirt (2.5.0-3ubuntu1) zesty; urgency=medium
* Merged with Debian unstable
- this picks up a fix for migrations using NFS mounts (LP: #1637601).
* Remaining changes:
- Disable sheepdog (universe dependency)
** Changed in: libvirt
Status: Incomplete => Fix Released
--
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
> I still remember the internal process and its mirroring :-)
I got you now.. ;-) [1]
BTW, just checked in BTS how Guido would like to proceed w/ this one
since the last patch (v3) submission ~1.5 weeks ago. Waiting.
[1] https://insights.ubuntu.com/author/paelzer/
--
You received this bug
On Mon, Nov 21, 2016 at 12:31 PM, Mauricio Faria de Oliveira <
mauri...@linux.vnet.ibm.com> wrote:
> BTW, I have to post some status/progress updates in this bug for
> internal tracking by other people; not meant at you. :)
>
I still remember the internal process and its mirroring :-)
Thanks for
Hi @Christian.
Cool. good news.
BTW, I have to post some status/progress updates in this bug for
internal tracking by other people; not meant at you. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI - @Mauricio - I'm tracking the Debian bug on my own and since a
libvirt merge is about to happen some-when next time anyway. If timing
works I intend to just do the merge after your change has been released
in Debian.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: libvirt
Status: Unknown => Incomplete
--
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
** Bug watch added: Debian Bug tracker #844339
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844339
** Also affects: libvirt via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844339
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Submitted patch v2 for Debian, addressing changes requested by Guido.
(but not yet the getent/adduser concern of debian bug 621833, which I decided
to first ask him about, so not to mix the changes upfront)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> There was a lot of extra mirroring on this - another bugproxy issue?
Probably. Apologies for you getting that. Please disregard it. :/
> Also while I know the maintainer scripts already have the same issue
> I today accidentally came by this
>
There was a lot of extra mirroring on this - another bugproxy issue?
** Bug watch added: Debian Bug tracker #621833
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621833
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also while I know the maintainer scripts already have the same issue I
today accidentally came by this https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=621833#174
I just wanted to mention if you think it would be worth to consider to
modify your adduser/addgroup calls with that insight.
And as
The attachment "xenial_libvirt_uidgid_v2.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the
For reference,
Debian bug for libvirt is #844339
--
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
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"
Hi Christian Ehrhardt,
> Sorry to realize that only now, but please help me to clarify/avoid
these issues?
no problem; sure.
> #1 On a given Xenial install as of today the files are owned by
> libvirt-qemu:kvm (e.g. pools and images it creates).
> Those files will still be owned by group
@Mauricio Faria de Oliveira - with the passwd change in I looked deeper
into the proposed libvirt debdiff - Sorry to realize that only now, but
please help me to clarify/avoid these issues?
While overall I think it is a great fix to define a known uid/gid I'm
not so happy with the fact that it
Thanks Colin for making the allocation and outlining the details of
base-passswd handling.
--
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
This bug was fixed in the package base-passwd - 3.5.41
---
base-passwd (3.5.41) unstable; urgency=medium
* Allocate uid/gid 64055 for libvirt guest migration support, by request
of Mauricio Faria de Oliveira (closes: #843881, LP: #1637601).
-- Colin Watson
I've made this allocation; see the Debian bug for details. Please note
that it is *not* necessary to take any special steps to upload base-
passwd to Ubuntu first, and you should definitely not waste time SRUing
base-passwd to update the registry; all that is necessary is that the
registry held
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
On Wed, Nov 9, 2016 at 6:48 PM, Mauricio Faria de Oliveira <
mauri...@linux.vnet.ibm.com> wrote:
> I had in mind to submit the patch for Debian libvirt if/once the
> allocation request is granted on Debian. Of course, I can submit in
> advance and mention it's awaiting for base-passwd.
>
I
Hi @paelzer,
Thanks!
I had in mind to submit the patch for Debian libvirt if/once the
allocation request is granted on Debian. Of course, I can submit in
advance and mention it's awaiting for base-passwd.
Could you help w/ the base-passwd process? I believe it's @cjwatson who
handles this on
Just skimming over the issue and the proposed solution I'm ok
considering for libvirt provided that the change is ok and gone into
base-passwd. Adding that as a task to make that clear.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
@Mauricio - thanks for your great pre-work on this!
You mentioned you push to Debian - do you also have a debian bug already that
we should/could link?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The previous comment mentions a test-case and pattern, which were missing.
Here they are:
Test-case
===
Package is not installed -- no libvirt-qemu user/group:
---
# getent passwd libvirt-qemu
#
# getent group libvirt-qemu
#
Package is installed -- libvirt-qemu user/group is created w/
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
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
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 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
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
54 matches
Mail list logo
