This bug was fixed in the package libvirt - 0.7.5-5ubuntu27.22
---
libvirt (0.7.5-5ubuntu27.22) lucid-proposed; urgency=low
* Don't override local removal of default network autostart on upgrades
(LP: #372001)
- re-enable debian/Don-t-enable-default-network-on-boot.patch
Hello Jamin, or anyone else affected,
Accepted libvirt into lucid-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
libvirt version 0.7.5-5ubuntu27.22 fixes the issue on Lucid. Many
thanks.
** 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/372001
This bug was fixed in the package libvirt - 0.9.2-4ubuntu15.2
---
libvirt (0.9.2-4ubuntu15.2) oneiric-proposed; urgency=low
* Don't override local removal of default network autostart on upgrades
(LP: #372001)
- re-enable debian/Don-t-enable-default-network-on-boot.patch
libvirt version 0.9.2-4ubuntu15.2 fixes the issue on Oneiric. Many
thanks.
** Tags removed: verification-needed
** Tags added: verification-done-oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-done-oneiric
** 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/372001
Title:
default network autostart symlink recreated
To manage
Thanks Simon, I want to do extensive testing myself first (since I
messed up the first time), but will aim to get this uploaded today.
Hopefully it will hit the archive tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Jamin, or anyone else affected,
Accepted libvirt into oneiric-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
@Serge, whenever you are ready for this I'll be available to test,
thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372001
Title:
default network autostart symlink recreated
To manage
** Branch linked: lp:ubuntu/libvirt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372001
Title:
default network autostart symlink recreated
To manage notifications about this bug go to:
Serge, sorry for the late reply, I forgot to subscribe. I'll be
available to test both upgrade and fresh install behaviour of your patch
when it will be ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Simon,
thanks. As everyone (including SRU team) will likely be out for a good
chunk of the rest of the month, do you mind if we wait until early
january to do it?
I'm fine either way, but would prefer this not to slip through the
cracks or get out of sync on account of the holidays.
--
You
Works for me as the problem only manifests when updating libvirt and if
the SRU team will be out for holidays there shouldn't be any update
causing the default network to re-appear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My postinst patch was bad. I will re-upload a proper fix after it gets
more testing in precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372001
Title:
default network autostart symlink
** Changed in: libvirt (Ubuntu Maverick)
Status: New = Won't Fix
** Changed in: libvirt (Ubuntu Natty)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372001
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372001
Title:
default network autostart symlink recreated
To manage notifications about this bug go to:
** Also affects: libvirt (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu
This bug was fixed in the package libvirt - 0.9.7-2ubuntu3
---
libvirt (0.9.7-2ubuntu3) precise; urgency=low
* Don't override local removal of default network autostart on upgrades
(LP: #372001)
- re-enable debian/Don-t-enable-default-network-on-boot.patch
-
** Description changed:
- Periodically the autostart symlink for libvirt-bin's default network is
- recreated. This is not expected or desired behavior. I've manually
- removed the symlink repeatedly as I've created my own network
- definitions that I'd prefer were started instead.
+
Serge, you seem to have addressed this in Precise
(http://changelogs.ubuntu.com/changelogs/pool/main/libv/libvirt/libvirt_0.9.7-2ubuntu2/changelog).
Would that be possible to do a SRU for Lucid ? I'd like to test your fix
on Precise but I lack a test setup ATM.
Thanks for addressing this anyways.
Oops, I misread the fix that in fact no longer apply the patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372001
Title:
default network autostart symlink recreated
To manage notifications
@Simon,
do you think we should be applying debian/Don-t-enable-default-network-
on-boot.patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372001
Title:
default network autostart symlink
I do think that fix should be SRU-able, but I want to do a whole lot of
testing of new installs and upgrades before committing that fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372001
Title:
Ah, I see. Enabling only that patch breaks automatic net setup on new
installs. So to fix this bug, we should enable that patch and fix
postinst to create the symlink on new install.
** Changed in: libvirt (Ubuntu)
Status: Fix Committed = Triaged
--
You received this bug notification
Here is the debdiff Im proposing to fix this bug. It tests fine for me
- new installs get the default network autostart symlink, upgrades do
not.
** Patch added: Proposed debdiff
I am also annoyed by that behaviour after every update of the package.
Adam's analysis in comment #7 is right and I think its suggestion should
be implemented.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Thanks Simon and Adam, what you suggest sounds reasonable.
Do you mind raising this as a bug against the debian package? (If you
do, I'll go ahead and do it).
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of
I am also annoyed by that behaviour after every update of the package.
Adam's analysis in comment #7 is right and I think its suggestion should
be implemented.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Simon and Adam, what you suggest sounds reasonable.
Do you mind raising this as a bug against the debian package? (If you
do, I'll go ahead and do it).
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of
This is happening because the package is shipping the symlink as a
conffile. Generally speaking, this isn't a great idea, and dpkg's
handling of symlink-as-conffile cases is shockingly non-obvious.
Like most packages with symlink trees in /etc, what this should be doing
is not shipping the
This is happening because the package is shipping the symlink as a
conffile. Generally speaking, this isn't a great idea, and dpkg's
handling of symlink-as-conffile cases is shockingly non-obvious.
Like most packages with symlink trees in /etc, what this should be doing
is not shipping the
Every time you create a virtual machine, using virt-manager, it will be
started again. Maybe that's the case here?
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Every time you create a virtual machine, using virt-manager, it will be
started again. Maybe that's the case here?
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: libvirt (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) = (unassigned)
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
** Changed in: libvirt (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) = (unassigned)
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Jamin, is the network recreated if you undefine the default network with:
$ virsh net-destroy default
$ virsh net-undefine default
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
I don't want them undefined or removed, only not set to auto start.
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Confirmed
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Jamin, is the network recreated if you undefine the default network with:
$ virsh net-destroy default
$ virsh net-undefine default
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
I don't want them undefined or removed, only not set to auto start.
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Confirmed
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Confirmed
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Confirmed
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
**
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Steps to reproduce:
Create additional network definitions. I have the following (all set to start
on boot):
- public_1, 192.168.51.0/24, 192.168.51.128, 192.168.51.254, w/NAT
- private_1, 192.168.61.0/24, 192.168.61.128, 192.168.61.254, isolated
- private_2, 192.168.62.0/24, 192.168.62.128,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
**
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Steps to reproduce:
Create additional network definitions. I have the following (all set to start
on boot):
- public_1, 192.168.51.0/24, 192.168.51.128, 192.168.51.254, w/NAT
- private_1, 192.168.61.0/24, 192.168.61.128, 192.168.61.254, isolated
- private_2, 192.168.62.0/24, 192.168.62.128,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/26335916/Dependencies.txt
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
50 matches
Mail list logo
