Re: [Bug 1637601] Comment bridged from LTC Bugzilla

2017-01-16 Thread ChristianEhrhardt
On Mon, Jan 16, 2017 at 9:58 PM, bugproxy  wrote:

> Yes, it does work OK on Zesty for me too.
>

Great to hear that.


> How would you prefer to handle this for Xenial -- myself or yourself to
> provide a backport of changes in Debian/Zesty?
>

You did almost all the work so far, no need to take things away from you.
The steps to go for the SRU would not need to go via Debian again since
Xenial is released already.
To to provide this for xenial follow
https://wiki.ubuntu.com/StableReleaseUpdates.

I can review and upload the libvirt part, but we again need help for
baser-passwd.
The SRU Teamplate will help the SRU Team to make sure we considered
regressions and that severity is worth an update into a released Ubuntu
version.

So in some Detail:
1. you provide a debdiff for Xenial base-passwd
2. you provide a debdiff for Xenial libvirt
3. you fill the SRU Template and add it to the bug description here.
4. Together we will find a sponsor for base-passwd
5. SRU Team will evaluate and accept base-passwd
6. One of us can Test if base-passwd in proposed is as it should
7. I can upload libvirt for you
8. SRU Team will evaluate and accept libvirt
9. We check proposed for the full solution
Done, finally :-)

Since the code in libvirt is written defensively (not fatal error if
base-passwd update isn't there yet) both can actually progress at the same
time safely.
So 4-6 and 7-9 can run concurrently.

For 1&2 please we should start with you confirming if your attached:
https://launchpadlibrarian.net/293402521/xenial_libvirt_uidgid_v2.debdiff
https://launchpadlibrarian.net/291206174/xenial_base-passwd_libvirt.debdiff
are the latest and most up to date that shall be reviewed by me and then
the SRU Team?

E.g. the version numbers are not following what they should be yet (see
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
).
Also since it went a bit back and forth you might want changes in them, so
I would like to have a confirmation of bing up-to-date first.

If you need more help let me know, but you handled all so well until now,
there is no need to fully take over that IMHO.

-- 
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:
https://bugs.launchpad.net/libvirt/+bug/1637601/+subscriptions

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


[Bug 1637601] Comment bridged from LTC Bugzilla

2017-01-16 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2017-01-16 14:45 EDT---
Christian,

> 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) gid=116(kvm) groups=116(kvm),64055(libvirt-qemu)

Yes, it does work OK on Zesty for me too.

How would you prefer to handle this for Xenial -- myself or yourself to
provide a backport of changes in Debian/Zesty?

Thanks!

Details
--

Distro and Package version
---

# lsb_release -d
Description:Ubuntu Zesty Zapus (development branch)

# apt-cache madison libvirt-daemon-system
libvirt-daemon-system | 2.5.0-3ubuntu1 | 
http://us.ports.ubuntu.com/ubuntu-ports zesty/main ppc64el Packages

Install without existing user/group (set UID/GID)
---

# id libvirt-qemu
id: ?libvirt-qemu?: no such user

# apt-get install --yes --no-install-recommends libvirt-daemon-system

# id libvirt-qemu
uid=64055(libvirt-qemu) gid=117(kvm) groups=117(kvm),64055(libvirt-qemu)

Install with existing user/group (keep UID/GID)
---

# apt-get purge --yes libvirt-daemon-system

# id libvirt-qemu
id: ?libvirt-qemu?: no such user

# useradd --system --no-create-home --uid 1704 libvirt-qemu

# id libvirt-qemu
uid=1704(libvirt-qemu) gid=999(libvirt-qemu) groups=999(libvirt-qemu)

# apt-get install --yes --no-install-recommends libvirt-daemon-system

# id libvirt-qemu
uid=1704(libvirt-qemu) gid=999(libvirt-qemu) groups=999(libvirt-qemu)

-- 
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:
https://bugs.launchpad.net/libvirt/+bug/1637601/+subscriptions

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


[Bug 1637601] Comment bridged from LTC Bugzilla

2017-01-12 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2017-01-12 18:07 EDT---
Hi Christian,

> 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

Sure. Sorry for the delay. Catching up from vacation. Should be able to
test this soon! Thanks.

-- 
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:
https://bugs.launchpad.net/libvirt/+bug/1637601/+subscriptions

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


[Bug 1637601] Comment bridged from LTC Bugzilla

2016-10-31 Thread bugproxy
--- Comment From lagar...@br.ibm.com 2016-10-31 19:06 EDT---
*** Bug 147941 has been marked as a duplicate of this bug. ***

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1637601/+subscriptions

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