Even on a fresh Xenial container with Xenial level libvirt the issue is not
reproducible.
So it seems that was an issue local to my initial test system (a xenial lxd
container onas well but on a test system driven by jenkins).
The retest was a simple:
1. xenial container
2. uvtool 3 guests
3. kill guest2 one
4. restart libvirt
5. start guest2
The ports gone and reallocated were all good.
We make some slight extra configs in the jenkins driven tests, but none of them
were bviously related. I'll mark this incomplete here - if a user comes with a
different case triggering this or it persists in the automated testing we need
to find what the difference to the simple case is.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717442
Title:
VNC auto port allocation affected by daemon state
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1717442/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
