[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.2 --- libvirt (2.5.0-3ubuntu5.2) zesty; urgency=medium * d/p/ubuntu/qemu_process-spice-don-t-release-used-port.patch: qemu_process spice: don't release used port (LP: #1697729) - upstream in libvirt 3.1. -- Christian

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

untwisted my verification tag - sorry ** Tags removed: verification-zesty-done ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697729 Title: port allocator

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.2~cloud0 --- libvirt (2.5.0-3ubuntu5.2~cloud0) xenial-ocata; urgency=medium . * New update for the Ubuntu Cloud Archive. . libvirt (2.5.0-3ubuntu5.2) zesty; urgency=medium . *

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.2~cloud0 --- libvirt (2.5.0-3ubuntu5.2~cloud0) xenial-ocata; urgency=medium . * New update for the Ubuntu Cloud Archive. . libvirt (2.5.0-3ubuntu5.2) zesty; urgency=medium . *

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Sorry, My comment had the incorrect package version. I'm running 2.5.0-3ubuntu5.2~cloud0 from ocata proposed and it fixes the issue for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697729

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Confirmed 2.5.0-3ubuntu9~cloud0 from ocata-proposed works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697729 Title: port allocator allocates the same SPICE port for multiple guests (race

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

I can say that the package in zesty-proposed resolves the issue for me. I did not go through the test case but was happy to see this bug fixed in proposed (for some reason today I started losing the race all the time; annoying but thankful at the same time! :). -- You received this bug

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

** Tags removed: 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/1697729 Title: port allocator allocates the same SPICE port for multiple guests (race condition) To manage

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

This bug was fixed in the package libvirt - 2.5.0-3ubuntu9~cloud0 --- libvirt (2.5.0-3ubuntu9~cloud0) xenial-pike; urgency=medium . * New update for the Ubuntu Cloud Archive. . libvirt (2.5.0-3ubuntu9) artful; urgency=medium . *

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

This bug was fixed in the package libvirt - 2.5.0-3ubuntu9~cloud0 --- libvirt (2.5.0-3ubuntu9~cloud0) xenial-pike; urgency=medium . * New update for the Ubuntu Cloud Archive. . libvirt (2.5.0-3ubuntu9) artful; urgency=medium . *

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Per former comment also setting verification-done for Pike. Also making clear in the tags that the general v-d was for zesty. Thanks Alexander for checking. ** Tags removed: verification-pike-needed ** Tags added: verification-pike-done verification-zesty-done -- You received this bug

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Hi, I recreated the issue in our environment with: 2.5.0-3ubuntu5~cloud0. The first time I attempted to provision 10 instances at the same time many errorred out with the same error described in the bug report (qemu- system-x86_64: failed to initialize spice server) I upgraded to:

Re: [Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

On Wed, Jun 21, 2017 at 6:49 PM, Aaron Johnson wrote: > Is there any chance you could get this pushed into xenial-proposed as > well? > Hi Aaron, Xenial itself is not affected - you might be on a Ubuntu Cloud Archive on Xenial and you can then test that. James made one

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

I would like to test this but right now we are running Xenial... Is there any chance you could get this pushed into xenial-proposed as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697729

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Tested proposed, working as it did in the PPA. Setting verification-done. @Aaron - if you can please verify as well in your context. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Hello Aaron, or anyone else affected, Accepted libvirt into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/2.5.0-3ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Tests on Zesty are good as well, we have: - regression tests on ppa ok - bug fix on ppa confirmed - added case to regular testing - dep8's seem to be happy as well [1] - SRU Template is complete That said pushing for SRU review now [2]. [1]: https://bileto.ubuntu.com/excuses/2825/zesty.html [2]:

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

** Changed in: libvirt (Ubuntu Zesty) Status: Triaged => In Progress ** Changed in: libvirt (Ubuntu Zesty) Assignee: (unassigned) => ChristianEhrhardt (paelzer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

FYI qemu/libvirt tests now have this and a few other concurrent start/stop tests to check for known (this) and unknown races - the architecture should be easy to extend for more cases as we want to add them (modify uvt template + function = test). Stage 3 is not yet part of daily but will

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

FYI - the dependent cockpit test had a few unrelated hickups. I discussed with pitti who maintains cockpit and we agreed that short term retrying until passed is ok, but he will look into it. We shared a bit of the local repro experience and it passed for artful on the second retry. -- You

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

This bug was fixed in the package libvirt - 2.5.0-3ubuntu9 --- libvirt (2.5.0-3ubuntu9) artful; urgency=medium * d/p/ubuntu/qemu_process-spice-don-t-release-used-port.patch: qemu_process spice: don't release used port (LP: #1697729) - upstream in libvirt 3.1. -- Christian

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Actually as lessons learned we need a somewhat extended concurrent start test - with more guest options ... looking into that now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697729 Title: port

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Manual tests on Zesty succeeded, regression tests running. ** Description changed: [Impact] - * VMs start to fail depending on a race around spice port allocation +  * VMs start to fail depending on a race around spice port allocation - * Solution is the Backport of an upstream fix

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

In Artful-proposed [1] now, and Zesty SRU is prepared in [2] for regression tests series. [1]: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html [2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2825 -- You received this bug notification because

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

In theory this could exist back to Xenial as well (the double cleanup is there), but the cleanup code was changed later which could affect the race. Also we so far got no reports on this pre Ocata/Zesty so for now do not push further back than Zesty. >From the Upstream/Redhat Tests it was also

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

[Impact] * libvirt sporadically throws the following error and can be seen in nova-compute.log: 2017-06-12 14:32:54.359 19007 ERROR nova.compute.manager [instance: d1af2a13-0a53-4d9c-ada3-683e4973f28a] libvirtError: internal error: process exited while connecting to monitor: ((null):63256):

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Thanks for all the pre-work Aaron! Thanks James for refiling against libvirt and pinging me. Lets test in a ppa and run all sorts of regression tests against it this week. If all works out I should be able to push to Artful early next week and consider SRUs from there. For now I build the fix

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

** Tags added: openstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697729 Title: port allocator allocates the same SPICE port for multiple guests (race condition) To manage notifications

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

https://libvirt.org/git/?p=libvirt.git;a=commit;h=c23b7b81db58c61b0adc98095dca7bfbad74fa79 ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Checked libvirt source from Artful: $ fgrep -r "virPortAllocatorRelease(driver->remotePorts, port);" * src/qemu/qemu_process.c:virPortAllocatorRelease(driver->remotePorts, port); ** Changed in: libvirt (Ubuntu) Importance: Undecided => High ** Changed in: libvirt (Ubuntu) Status:

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

https://libvirt.org/git/?p=libvirt.git;a=commit;h=c23b7b81db58c61b0adc98095dca7bfbad74fa79 ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Also confirmed on Zesty libvirt ** Changed in: libvirt (Ubuntu Zesty) Status: Confirmed => Triaged ** Changed in: libvirt (Ubuntu Artful) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1697729] Re: port allocator allocates the same SPICE port for multiple guests (race condition)

Checked libvirt source from Artful: $ fgrep -r "virPortAllocatorRelease(driver->remotePorts, port);" * src/qemu/qemu_process.c:virPortAllocatorRelease(driver->remotePorts, port); ** Changed in: libvirt (Ubuntu) Importance: Undecided => High ** Changed in: libvirt (Ubuntu) Status: