[Bug 798844] Re: Chef integration
** Changed in: cloud-init (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/798844 Title: Chef integration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/798844/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 813901] Re: package qemu-kvm 0.12.5 dfsg-5 squeeze1 failed to install/upgrade: Versuch, »/usr/share/man/man1/qemu-img.1.gz« zu überschreiben, welches auch in Paket qemu-utils 0.12.5 dfsg-3 ist
Hi, I'm marking this invalid as it is a bug resulting from installing a non-ubuntu package on ubuntu. That said, I understand that your primary reason for attempting this is that there are no openbios binaries in qemu-kvm on Ubuntu. Could you please open a new bug to that effect? I'm possibly missing something, but it seems like the right path may be to open bugs against openbios-sparc [1] and openbios-ppc [2] are not sufficient, which are currently fail to build from source (FTBFS). [1] https://launchpad.net/ubuntu/+source/openbios-sparc [2] https://launchpad.net/ubuntu/+source/openbios-ppc ** Changed in: qemu-kvm (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/813901 Title: package qemu-kvm 0.12.5 dfsg-5 squeeze1 failed to install/upgrade: Versuch, »/usr/share/man/man1/qemu-img.1.gz« zu überschreiben, welches auch in Paket qemu-utils 0.12.5 dfsg-3 ist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/813901/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 798844] Re: Chef integration
** Changed in: cloud-init (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/798844 Title: Chef integration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/798844/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 766242] Re: lp:ubuntu/cloud-init is not buildable by bzr-builder
I'm moving this to confirmed in bzr-builder. That said, I would be willing to have the lp:ubuntu/cloud-init branch fixed because I'd like for it to build. I personally really hate .pc directories being versioned, but would live with it or consider moving off quilt-3.0. somewhat related, is that cloud-init is on the failed importer list [http://package-import.ubuntu.com/status/]. I *think* that if we just wiped all ubuntu/cloud-init history, and re-imported from scratch, both that issue and this issue would be resolved. ** Changed in: bzr-builder Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/766242 Title: lp:ubuntu/cloud-init is not buildable by bzr-builder To manage notifications about this bug go to: https://bugs.launchpad.net/bzr-builder/+bug/766242/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 812646] Re: Race in DataSourceNoCloudNet with kvm
** Branch linked: lp:ubuntu/cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/812646 Title: Race in DataSourceNoCloudNet with kvm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/812646/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 812539] Re: FQDN does not get set correctly in /etc/hosts
** Branch linked: lp:ubuntu/cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/812539 Title: FQDN does not get set correctly in /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/812539/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 797336] Re: byobu-by-default cannot be disabled via cloud-config
** Branch linked: lp:ubuntu/cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/797336 Title: byobu-by-default cannot be disabled via cloud-config To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/797336/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 761847] Re: cloud-init does not work in eucalyptus SYSTEM or STATIC modes
** Branch linked: lp:ubuntu/cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/761847 Title: cloud-init does not work in eucalyptus SYSTEM or STATIC modes To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/761847/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 798844] Re: Chef integration
** Branch linked: lp:ubuntu/cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/798844 Title: Chef integration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/798844/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 800856] Re: resizefs module causes problems on LXC containers
** Branch linked: lp:ubuntu/cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/800856 Title: resizefs module causes problems on LXC containers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/800856/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 744019] Re: mountall errors on boot
** Branch linked: lp:ubuntu/cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/744019 Title: mountall errors on boot To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/744019/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 812646] Re: Race in DataSourceNoCloudNet with kvm
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu12 --- cloud-init (0.6.1-0ubuntu12) oneiric; urgency=low * do not give trace on failure to resize in lxc container (LP: #800856) * increase the timeout on url gets for seedfrom values (LP: #812646) * do not write entries for ephemeral0 on t1.micro (LP: #744019) [Adam Gandalman] * improve the updating of /etc/hosts with correct fqdn when possible (LP: #812539) [Avishai Ish-Shalom] * add chef support (cloudinit/CloudConfig/cc_chef.py) (LP: #798844) -- Scott Moser smo...@ubuntu.com Thu, 21 Jul 2011 05:51:03 -0400 ** Changed in: cloud-init (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/812646 Title: Race in DataSourceNoCloudNet with kvm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/812646/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 812539] Re: FQDN does not get set correctly in /etc/hosts
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu12 --- cloud-init (0.6.1-0ubuntu12) oneiric; urgency=low * do not give trace on failure to resize in lxc container (LP: #800856) * increase the timeout on url gets for seedfrom values (LP: #812646) * do not write entries for ephemeral0 on t1.micro (LP: #744019) [Adam Gandalman] * improve the updating of /etc/hosts with correct fqdn when possible (LP: #812539) [Avishai Ish-Shalom] * add chef support (cloudinit/CloudConfig/cc_chef.py) (LP: #798844) -- Scott Moser smo...@ubuntu.com Thu, 21 Jul 2011 05:51:03 -0400 ** Changed in: cloud-init (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/812539 Title: FQDN does not get set correctly in /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/812539/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 800856] Re: resizefs module causes problems on LXC containers
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu12 --- cloud-init (0.6.1-0ubuntu12) oneiric; urgency=low * do not give trace on failure to resize in lxc container (LP: #800856) * increase the timeout on url gets for seedfrom values (LP: #812646) * do not write entries for ephemeral0 on t1.micro (LP: #744019) [Adam Gandalman] * improve the updating of /etc/hosts with correct fqdn when possible (LP: #812539) [Avishai Ish-Shalom] * add chef support (cloudinit/CloudConfig/cc_chef.py) (LP: #798844) -- Scott Moser smo...@ubuntu.com Thu, 21 Jul 2011 05:51:03 -0400 ** Changed in: cloud-init (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/800856 Title: resizefs module causes problems on LXC containers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/800856/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 798844] Re: Chef integration
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu12 --- cloud-init (0.6.1-0ubuntu12) oneiric; urgency=low * do not give trace on failure to resize in lxc container (LP: #800856) * increase the timeout on url gets for seedfrom values (LP: #812646) * do not write entries for ephemeral0 on t1.micro (LP: #744019) [Adam Gandalman] * improve the updating of /etc/hosts with correct fqdn when possible (LP: #812539) [Avishai Ish-Shalom] * add chef support (cloudinit/CloudConfig/cc_chef.py) (LP: #798844) -- Scott Moser smo...@ubuntu.com Thu, 21 Jul 2011 05:51:03 -0400 ** Changed in: cloud-init (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/798844 Title: Chef integration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/798844/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 744019] Re: mountall errors on boot
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu12 --- cloud-init (0.6.1-0ubuntu12) oneiric; urgency=low * do not give trace on failure to resize in lxc container (LP: #800856) * increase the timeout on url gets for seedfrom values (LP: #812646) * do not write entries for ephemeral0 on t1.micro (LP: #744019) [Adam Gandalman] * improve the updating of /etc/hosts with correct fqdn when possible (LP: #812539) [Avishai Ish-Shalom] * add chef support (cloudinit/CloudConfig/cc_chef.py) (LP: #798844) -- Scott Moser smo...@ubuntu.com Thu, 21 Jul 2011 05:51:03 -0400 ** Changed in: cloud-init (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/744019 Title: mountall errors on boot To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/744019/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814058] [NEW] [#313217] runscript crash when using environment variable in script
Public bug reported: I entered a bug a patch in the upstream version : https://alioth.debian.org/tracker/index.php?func=detailaid=313217group_id=30018atid=100031 Can you integrate the fix for the next release ? Thanks :) ** Affects: minicom (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to minicom in Ubuntu. https://bugs.launchpad.net/bugs/814058 Title: [#313217] runscript crash when using environment variable in script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/minicom/+bug/814058/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 630343] Re: package open-vm-dkms 2010.02.23-236320-1+ubuntu1 failed to install/upgrade: open-vm-tools kernel module failed to build
Hi, I've tried to reproduce this on a fresh, uptodate 10.04 lucid server install with 2.6.32-24-server. But apt-get install open-vm-dkms succeeded for me. I notice that even though the bug description lists 2.6.32, the buildlog (for this bug and all dupes) shows: make[1]: Entrando no diretório `/usr/src/linux- headers-2.6.35-17-generic' Please uninstall linux-headers-2.6.35 and re-install linux-headers- server or linux-headers-generic. I am going to mark this bug invalid, as the dkms packages necessarily must be targeted at the default kernel. ** Changed in: open-vm-tools (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/630343 Title: package open-vm-dkms 2010.02.23-236320-1+ubuntu1 failed to install/upgrade: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/630343/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 629925] Re: package open-vm-dkms 2010.04.25-253928-2 ubuntu2 failed to install/upgrade: open-vm-tools kernel module failed to build (maverick)
Although you are on a 2.6.35 kernel, the dkms build log shows make[1]: Entering directory `/usr/src/linux-headers-2.6.32-25-generic' Please uninstall any linux-headers packages, and install the default using apt-get install linux-headers-generic I am going to mark this bug invalid, but please do respond if you need more help. ** Changed in: open-vm-tools (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/629925 Title: package open-vm-dkms 2010.04.25-253928-2 ubuntu2 failed to install/upgrade: open-vm-tools kernel module failed to build (maverick) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/629925/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 495394] Re: autostart almost always fails on boot time host
** Description changed: = SRU justification: 1. Impact: servers which auto-start libvirt VMs can result in failed -VM boots if network devices involved have not been brought up in -time. + VM boots if network devices involved have not been brought up in + time. 2. How bug is addressed: the libvirt-bin.conf upstart job now waits -until networking.conf (ifup -a) is done, so that all network devices -have been brought up. + until networking.conf (ifup -a) is done, so that all network devices + have been brought up. 3. Minimal patch: --- libvirt-0.9.2/debian/libvirt-bin.upstart2011-06-23 10:12:47.0 -0500 +++ libvirt-0.9.2/debian/libvirt-bin.upstart2011-07-07 10:23:20.0 -0500 @@ -1,7 +1,7 @@ - description libvirt daemon - author Dustin Kirkland kirkl...@canonical.com - + description libvirt daemon + author Dustin Kirkland kirkl...@canonical.com + -start on runlevel [2345] +start on (runlevel [2345] and stopped networking RESULT=ok) - stop on runlevel [!2345] - - expect daemon + stop on runlevel [!2345] - 4. Test case: -Add an entry to /etc/network/interfaces like: + expect daemon + + 4. TEST CASE: + Add an entry to /etc/network/interfaces like: auto lxcbr0 iface lxcbr0 inet static - pre-up /opt/sleep - bridge_ports none - address 192.168.30.1 - netmask 255.255.255.0 + pre-up /opt/sleep + bridge_ports none + address 192.168.30.1 + netmask 255.255.255.0 where /opt/sleep is an executable script sleeping 1 minute. Then define a libvirt VM with the following network: - interface type='bridge' - source bridge='lxcbr0'/ - target dev='veth0'/ - /interface + interface type='bridge' + source bridge='lxcbr0'/ + target dev='veth0'/ + /interface - (an lxc instance can be used as well as qemu) and link its definition - under /etc/libvirt/qemu/autostart/ or /etc/libvirt/lxc/autostart/. - On reboot, the VM will fail to start without this patch. + If reproducing inside a kvm VM, you can define a minimal non-kvm qemu + vm booting from a debian businesscard iso cdrom, or use an lxc instance. + Make the VM autostart using + +virsh autostart vmname # or virsh -c lxc:// autostart vmname + + On reboot, the VM will fail to start without this patch. With the patch, + for the first minute after reboot (while lxcbr0 is not yet configured) the + command + +status libvirt-bin + + will show libvirt is not yet running. When it starts, your vm will be running + as seen by + +virsh list # or virsh -c lxc:// list 5. Regression potential: If a site has auto network interfaces which are defined but always fail to start, then even though those interfaces may not be needed at all, libvirt will fail to start until the definitions are removed or fixed. = host OS: lsb_release -rd: 1. Release of Ubuntu: Description: Ubuntu 9.10 Release: 9.10 Linux 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux 2. Version of package: apt-cache policy libvirt-bin libvirt-bin: Installed: 0.7.0-1ubuntu13.1 Candidate: 0.7.0-1ubuntu13.1 Version table: *** 0.7.0-1ubuntu13.1 0 500 http://nl.archive.ubuntu.com karmic-updates/main Packages 100 /var/lib/dpkg/status 0.7.0-1ubuntu13 0 500 http://nl.archive.ubuntu.com karmic/main Packages 3. What I expected to happen: Domains that are marked `autostart' should be running after the host was booted. 4. What happened instead: - auto starting domains mostly fails when booting the host OS (Ubuntu 9.10) - auto starting the same domains does work when using Ubuntu 8.04.3 LTS or Ubuntu 9.04 as host OS - auto starting the same domains does work when invoking `/etc/init.d/libvirt-bin restart' Libvirtd is running. There are symlinks in /etc/libvirt/qemu/autostart. Mostly none of my domains are running, however sometimes a domain succeeds and is booted (say 1 in 10 attempts a domain succeeds to boot during the host boot process). When, after booting the host, I run `/etc/init.d/libvirt-bin restart' all of my domains are coming up as expected. Autostart works for all domains while using Ubuntu 8.04.3 LTS or Ubuntu 9.04 as host OS. I'm using Ubuntu 9.04 and 9.10 guest OS'es. Some of them were created under Ubuntu 9.04 and some of them were created on Ubuntu 9.10. Most of the domains are installed on a LVM, but I also tried creating a file based virtual machine that is located on the boot device of the host OS. There is no difference between these domains, all of them are booted only very sporadicly while booting the host OS. All domains are using a bridge device that I specified myself, and using static IP addresses. I removed the default network created by
[Bug 690387] Re: udev block naming breaks failover and sd kref release cycle
@Serge Yes, fix-released for oneiric I believe natty is covered. The confusion I think is the changelog references this fix from a private bug: multipath-tools (0.4.8-14ubuntu7) natty; urgency=low * Add patch to fix the expected pathname from multipath uevents (LP: #660597) Where this bug, lp #690387 is the public instance of the fix. Though in lucid, I don't see either bug number mentioned in the changelog. multipath-tools (0.4.8-14ubuntu4.10.04.1) lucid-proposed; urgency=high * Eliminate UDEV CHANGE events generated by mpath priority checkers. Due to quirk in how SG IO is handled by SD devices (LP: #644489). -- Peter M. Petrakis peter.petra...@canonical.com Tue, 21 Jun 2011 14:13:12 -0400 multipath-tools (0.4.8-14ubuntu4) lucid; urgency=low * debian/control: Move libreadline5-dev build dependency to libreadline-dev. (Already done in Debian). -- Martin Pitt martin.p...@ubuntu.com Mon, 08 Mar 2010 14:50:04 +0100 multipath-tools (0.4.8-14ubuntu3) lucid; urgency=low * Support failback for Intel Modular Server (LP: #520309). -- Colin Watson cjwat...@ubuntu.com Fri, 12 Feb 2010 12:21:42 + root@kickseed:~# apt-cache policy multipath-tools multipath-tools: Installed: 0.4.8-14ubuntu4.10.04.1 Candidate: 0.4.8-14ubuntu4.10.04.1 Version table: 0.4.8-14ubuntu10.1 0 800 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main Packages 0.4.8-14ubuntu10 0 800 http://us.archive.ubuntu.com/ubuntu/ natty/main Packages *** 0.4.8-14ubuntu4.10.04.1 0 900 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 0.4.8-14ubuntu4 0 900 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages Do we have this pending SRU for lucid somewhere and lost track of it? http://people.canonical.com/~ubuntu-archive/pending-sru.html I don't see anything pending for multipath. Wasn't there a mass changeset planned for multipath lucid SRU that included this fix? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/690387 Title: udev block naming breaks failover and sd kref release cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/690387/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 812553] Re: LXC instance fails to start
** Branch linked: lp:~smoser/nova/lp812553 ** Changed in: nova Importance: Undecided = High ** Changed in: nova Status: New = Fix Committed ** Changed in: nova Assignee: (unassigned) = Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/812553 Title: LXC instance fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/812553/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 806176] Re: /usr/lib/pymodules/python2.6/nova/network/manager.py, line 558, in create_networks
** Changed in: nova Status: New = Invalid ** Changed in: nova (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/806176 Title: /usr/lib/pymodules/python2.6/nova/network/manager.py, line 558, in create_networks To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/806176/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 690387] Re: udev block naming breaks failover and sd kref release cycle
Thanks, Peter. I'll follow up on this bug. The mass SRU failed. Any high priority bugs not yet SRUd should be separately handled. Several of the bugs which were part of the mass SRU were not listed as high priority. If anyone feels they *are* high priority, then pls comment in the bugs to that effect, and we can pursue a (separate) SRU. ** Changed in: multipath-tools (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/690387 Title: udev block naming breaks failover and sd kref release cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/690387/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 690387] Re: udev block naming breaks failover and sd kref release cycle
** Also affects: multipath-tools (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: multipath-tools (Ubuntu Maverick) Importance: Undecided Status: New ** Also affects: multipath-tools (Ubuntu Natty) Importance: Undecided Status: New ** Changed in: multipath-tools (Ubuntu Lucid) Importance: Undecided = High ** Changed in: multipath-tools (Ubuntu Maverick) Importance: Undecided = High ** Changed in: multipath-tools (Ubuntu Natty) Importance: Undecided = High ** Changed in: multipath-tools (Ubuntu Lucid) Status: New = In Progress ** Changed in: multipath-tools (Ubuntu Maverick) Status: New = In Progress ** Changed in: multipath-tools (Ubuntu Natty) Status: New = In Progress ** Changed in: multipath-tools (Ubuntu Natty) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/690387 Title: udev block naming breaks failover and sd kref release cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/690387/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814164] [NEW] The init script does not handle the script-security parameter correctly when there are multiple configuration files
Public bug reported: When there are 2 or more VPN configuration files and one of them does not use the script-security parameter, the subsequent (alphabetic order) openvpn process will be called with --script-security 2 no matter what is the value of the script-security parameter in the configuration file. This behaviour only occurs when the init script processes many VPN configuration files in one call (on startup/restart). Example of the problem : # grep script-security patrick.conf zzz.conf zzz.conf:script-security 1 # /etc/init.d/openvpn restart # ps aux| grep openvpn openvpn 5705 0.4 0.0 37040 2812 ?Ss 12:27 0:00 /usr/sbin/openvpn --writepid /var/run/openvpn.patrick.pid --daemon ovpn-patrick --cd /etc/openvpn --config /etc/openvpn/patrick.conf --script-security 2 openvpn 5722 0.1 0.0 30968 2996 ?Ss 12:27 0:00 /usr/sbin/openvpn --writepid /var/run/openvpn.zzz.pid --daemon ovpn-zzz --cd /etc/openvpn --config /etc/openvpn/zzz.conf --script-security 2 The process for the zzz.conf VPN should have script-security 1 as the configuration file says but it's not the case. # lsb_release -rd Description:Ubuntu 11.04 Release:11.04 # apt-cache policy openvpn openvpn: Installed: 2.1.3-2ubuntu3 Candidate: 2.1.3-2ubuntu3 Version table: *** 2.1.3-2ubuntu3 0 500 http://ca.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: openvpn 2.1.3-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-11.47-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Thu Jul 21 11:31:48 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/814164 Title: The init script does not handle the script-security parameter correctly when there are multiple configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/814164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814164] Re: The init script does not handle the script-security parameter correctly when there are multiple configuration files
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/814164 Title: The init script does not handle the script-security parameter correctly when there are multiple configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/814164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 690387] Re: udev block naming breaks failover and sd kref release cycle
** Description changed: Binary package hint: multipath-tools + + + SRU Justification: + 1. Impact: multipath fail-over events are not handled by multipathd. The system therefore does not cleanly survive FOFB. + 2. How addressed: a bug from upstream is cherry-picked which fixes multipathd to look for the correct device pathnames in uevents it sees. + 3. Patch: see debdiff attached + 4. To reproduce: Start multipathd with -v4 argument. Reset an SCM to initiate FOFB. Watch /var/log/daemon.log for uevents relating to drives. Without the patch they don't show up. Additionally, upon failback, new block device names will be used (i.e. /dev/sdo instead of /dev/sda). + 5. Regression potential: the patch is to multipathd, so non-multipath users will not be affected. Multipathd users with an older kernel which uses the old pathanames could get the same behavior which uptodate users now have without this patch. + + This was exposed on the Intel IMS SAN which is an ODM'd Promise Vtrak variant on 10.04 server. The SAN has Active/Standby capabilities and is configured for failover. It probably affects other SANs too. Setup: multipath'd SAN consisting of SD block devices. Symptoms: On failover, multipath isn't gettng the right signals to tear down the defunct path. This was traced down to the fact that the path UDEV was presenting to multipath was different from what it was expecting. It simply dropped the request to gracefully remove the device, and instead responded to the SCSI mid-layer SD IO state change, SDEV_CANCEL/DEL which puts the device offline. Problem is device mapper still has an handle on the SD device, as can be seen from /sys/block/dm-x/slaves, and as a result, scsi_target_destroy is never called. The outward symptom of this is the SD suffix is not recycled because of course the previous reference never dropped. Solution: A fix was developed independently of upstream by Serge Hallyn, later it was found that it was fixed upstream, in 2008. The patch is: commit 7fa7affc3d23dd9dc906804d22a61144bca9f9b9 Author: Benjamin Marzinski bmarz...@redhat.com Date: Thu Dec 11 16:03:28 2008 -0600 Fix for uevent devpath handling This is necessary to make uevents work on fedora, since devpath appears as something like: '/devices/pci:00/:00:0a.0/:06:00.0/host11/rport-11:0-1/target11:0:1/11:0:1:0/block/s It simply strips off the everything up to the /block. Signed-off-by: Benjamin Marzinski bmarz...@redhat.com It integrates simply and can be found in PPAs here: ppa:peter-petrakis/storage -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/690387 Title: udev block naming breaks failover and sd kref release cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/690387/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 690387] Re: udev block naming breaks failover and sd kref release cycle
** Changed in: multipath-tools (Ubuntu Maverick) Status: In Progress = Fix Committed ** Changed in: multipath-tools (Ubuntu Lucid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/690387 Title: udev block naming breaks failover and sd kref release cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/690387/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814164] Re: The init script does not handle the script-security parameter correctly when there are multiple configuration files
Here is a patch that make sure the script-security parameter is handle properly for each VPN configuration files. ** Bug watch added: community.openvpn.net/openvpn/ #118 https://community.openvpn.net/openvpn/ticket/118 ** Also affects: openvpn via https://community.openvpn.net/openvpn/ticket/118 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/814164 Title: The init script does not handle the script-security parameter correctly when there are multiple configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/814164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814164] Re: The init script does not handle the script-security parameter correctly when there are multiple configuration files
I failed to attach the file in my previous comment. ** Patch added: Reset the script_security variable to avoid reusing it for other VPN configurations https://bugs.launchpad.net/openvpn/+bug/814164/+attachment/2223644/+files/openvpn-init.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/814164 Title: The init script does not handle the script-security parameter correctly when there are multiple configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/814164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 804593] Re: Many Safely remove icons on virtualized XPs
** Changed in: qemu-kvm (Ubuntu) Status: Incomplete = New ** Changed in: qemu-kvm (Ubuntu) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/804593 Title: Many Safely remove icons on virtualized XPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/804593/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814164] Re: The init script does not handle the script-security parameter correctly when there are multiple configuration files
** Changed in: openvpn Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/814164 Title: The init script does not handle the script-security parameter correctly when there are multiple configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/814164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814164] Re: The init script does not handle the script-security parameter correctly when there are multiple configuration files
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/814164 Title: The init script does not handle the script-security parameter correctly when there are multiple configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/814164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 776103] Re: package open-vm-dkms 2011.03.28-387002-0ubuntu2 fails to build against 2.6.39 kernels, due to missing linux/smp_lock.h
I am about to push new packaging that adds -Wno-unused-but-set- variable to the CFLAGS (in debian/rules). This comes at the suggestion of one of the developers over at SF. This hopes to solve issues with GCC 4.6.x. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/776103 Title: package open-vm-dkms 2011.03.28-387002-0ubuntu2 fails to build against 2.6.39 kernels, due to missing linux/smp_lock.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/776103/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814222] [NEW] kvm cannot use vhd files over 127GB
Public bug reported: The primary use case for using vhds with KVM is to perform a conversion to a raw image file so that one could move from Hyper-V to Linux-KVM. See more on this http://blog.allanglesit.com/2011/03/linux-kvm- migrating-hyper-v-vhd-images-to-kvm/ # kvm-img convert -f raw -O vpc /root/file.vhd /root/file.img The above works great if you have VHDs smaller than 127GB, however if it is larger, then no error is generated during the conversion process, but it appears to just process up to that 127GB barrier and no more. Also of note. VHDs can also be run directly using KVM if they are smaller than 127GB. VHDs can be read and function well using virtualbox as well as hyper-v, so I suspect the problem lies not with the VHD format (since that has a 2TB limitation). But instead with how qemu-kvm is interpreting them. BORING VERSION INFO: # cat /etc/issue Ubuntu 11.04 \n \l # uname -rmiv 2.6.38-8-server #42-Ubuntu SMP Mon Apr 11 03:49:04 UTC 2011 x86_64 x86_64 # apt-cache policy kvm kvm: Installed: 1:84+dfsg-0ubuntu16+0.14.0+noroms+0ubuntu4.1 Candidate: 1:84+dfsg-0ubuntu16+0.14.0+noroms+0ubuntu4.1 Version table: *** 1:84+dfsg-0ubuntu16+0.14.0+noroms+0ubuntu4.1 0 500 http://apt.sonosite.com/ubuntu/ natty-updates/main amd64 Packages 500 http://apt.sonosite.com/ubuntu/ natty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:84+dfsg-0ubuntu16+0.14.0+noroms+0ubuntu4 0 500 http://apt.sonosite.com/ubuntu/ natty/main amd64 Packages # apt-cache policy libvirt-bin libvirt-bin: Installed: 0.8.8-1ubuntu6.2 Candidate: 0.8.8-1ubuntu6.2 Version table: *** 0.8.8-1ubuntu6.2 0 500 http://apt.sonosite.com/ubuntu/ natty-updates/main amd64 Packages 500 http://apt.sonosite.com/ubuntu/ natty-security/main amd64 Packages 100 /var/lib/dpkg/status 0.8.8-1ubuntu6 0 500 http://apt.sonosite.com/ubuntu/ natty/main amd64 Packages qemu-img version 0.14.0 # vboxmanage -v 4.0.12r72916 REPRODUCTION STEPS (requires Windows 7 or Windows 2008 R2 with 1GB of free space) ## WINDOWS MACHINE ## Use Computer Management Disk Management -Create 2 VHD files, both dynamically expanding 120GB and 140GB respectively. -Do not initialize or format. These files will need to be transferred to an Ubuntu KVM machine (pscp is what I used but usb would work as well). ## UBUNTU KVM MACHINE ## # ls *.vhd 120g-dyn.vhd 140g-dyn.vhd # kvm-img info 120g-dyn.vhd image: 120g-dyn.vhd file format: vpc virtual size: 120G (128847052800 bytes) disk size: 244K # kvm-img info 140g-dyn.vhd image: 140g-dyn.vhd file format: vpc virtual size: 127G (13683600 bytes) disk size: 284K # kvm-img info 120g-dyn.vhd | grep virtual size virtual size: 120G (128847052800 bytes) # kvm-img info 140g-dyn.vhd | grep virtual size virtual size: 127G (13683600 bytes) Regardless of how big the second vhd is I always get a virtual size of 127G Now if we use virtualbox to view the vhds we see markedly different results. # VBoxManage showhdinfo 120g-dyn.vhd UUID: e63681e0-ff12-4114-85de-7d13562b36db Accessible: yes Logical size: 122880 MBytes Current size on disk: 0 MBytes Type: normal (base) Storage format: VHD Format variant: dynamic default Location: /root/120g-dyn.vhd # VBoxManage showhdinfo 140g-dyn.vhd UUID: 94531905-46b4-469f-bb44-7a7d388fb38f Accessible: yes Logical size: 143360 MBytes Current size on disk: 0 MBytes Type: normal (base) Storage format: VHD Format variant: dynamic default Location: /root/140g-dyn.vhd # kvm-img convert -f vpc -O raw 120g-dyn.vhd 120g-dyn.img # # kvm-img convert -f vpc -O raw 140g-dyn.vhd 140g-dyn.img # # kvm-img info 120g-dyn.img image: 120g-dyn.img file format: raw virtual size: 120G (128847052800 bytes) disk size: 0 # kvm-img info 120g-dyn.img | grep virtual size virtual size: 120G (128847052800 bytes) # kvm-img info 140g-dyn.img image: 140g-dyn.img file format: raw virtual size: 127G (13683600 bytes) disk size: 0 # kvm-img info 140g-dyn.img | grep virtual size virtual size: 127G (13683600 bytes) Notice after the conversion the raw image will the taken on the partial geometry of the vhd, thus rendering that image invalid. vboxmanage has a clonehd option which allows you to successfully convert vhd to a raw image, which kvm then sees properly. For giggles I also tested with a 140GB fixed VHD (in the same manner as above) and it displayed the virtual size as correct, so a good work around is to convert your VHDs to fixed, then use kvm-img to convert them. Keep in mind that these reproduction steps will not have a file systems therefore no valid data, if there were for example NTFS with a text file the problem would still occur but more importantly the guest trying to use it would not be able to open the disk because of it being unable to find the final sector. So
[Bug 814226] [NEW] package samba 2:3.5.8~dfsg-1ubuntu2.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: just want install samba. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: samba 2:3.5.8~dfsg-1ubuntu2.2 ProcVersionSignature: Ubuntu 2.6.38-11.47-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 AptOrdering: samba: Install samba: Configure Architecture: i386 Date: Thu Jul 21 13:32:57 2011 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) RelatedPackageVersions: nautilus 1:3.0.2-0ubuntu2~natty1 gvfs 1.8.0-0ubuntu2 SambaClientRegression: Yes SourcePackage: samba Title: package samba 2:3.5.8~dfsg-1ubuntu2.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 natty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/814226 Title: package samba 2:3.5.8~dfsg-1ubuntu2.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/814226/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814226] Re: package samba 2:3.5.8~dfsg-1ubuntu2.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/814226 Title: package samba 2:3.5.8~dfsg-1ubuntu2.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/814226/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 804593] Re: Many Safely remove icons on virtualized XPs
(Commits like 0965f12da61cbfe62252d21a8e6fa309753760e8: piix: tag as not hotpluggable, which are in natty, are supposed to prevent this) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/804593 Title: Many Safely remove icons on virtualized XPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/804593/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 804593] Re: Many Safely remove icons on virtualized XPs
(Still waiting for download to complete so I can reproduce, but) perhaps commit 505597e4476a6bc219d0ec1362b760d71cb4fdca: Ignore pci unplug requests for unpluggable devices (CVE-2011-1751) will help. ** CVE added: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2011-1751 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/804593 Title: Many Safely remove icons on virtualized XPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/804593/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
** Changed in: drbd8 (Ubuntu) Assignee: Andres Rodriguez (andreserl) = (unassigned) ** Changed in: drbd8 (Ubuntu) Status: In Progress = New ** Also affects: drbd8 (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: drbd8 (Ubuntu) Status: New = Fix Released ** Changed in: drbd8 (Ubuntu Lucid) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 668164] Re: package vsftpd 2.2.2-3ubuntu7.1 failed to install/upgrade: 子进程 已安装的 post-installation 脚本 返回了错误号 3
*** This bug is a duplicate of bug 523896 *** https://bugs.launchpad.net/bugs/523896 ** This bug is no longer a duplicate of bug 496601 package vsftpd 2.2.0-1ubuntu1 failed to install/upgrade: ??? post-installation ?? ?? 1 ** This bug has been marked a duplicate of bug 523896 useradd: cannot lock /etc/passwd; try again later. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/668164 Title: package vsftpd 2.2.2-3ubuntu7.1 failed to install/upgrade: 子进程 已安装的 post-installation 脚本 返回了错误号 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/668164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 496601] Re: package vsftpd 2.2.0-1ubuntu1 failed to install/upgrade: ??? ???? post-installation ?? ?????? 1
*** This bug is a duplicate of bug 523896 *** https://bugs.launchpad.net/bugs/523896 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 523896, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 523896 useradd: cannot lock /etc/passwd; try again later. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/496601 Title: package vsftpd 2.2.0-1ubuntu1 failed to install/upgrade: ??? post-installation ?? ?? 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/496601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814222] Re: kvm cannot use vhd files over 127GB
Thanks for taking the time to submit this bug. It looks like the 127G limit is known. A recent patch went in to help with the symptom you are seeing, but unfortunately it only makes the failure detectable :) It's a start at least. The following commit should be pulled in: commit 6e9ea0c0629fe25723494a19498bedf4b781cbfa Author: aurel32 aurel32@c046a42c-6fe2-441c-8c8c-71466251a162 Date: Wed Apr 15 14:42:46 2009 + block-vpc: Don't silently create smaller image than requested The algorithm from the VHD specification for CHS calculation silently limits images to 127 GB which may confuse a user who requested a larger image. Better output an error message and abort. Signed-off-by: Kevin Wolf kw...@redhat.com Signed-off-by: Aurelien Jarno aurel...@aurel32.net git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@7109 c046a42c-6fe2-441c-8c8c-71466251a162 ** Changed in: qemu-kvm (Ubuntu) Status: New = Confirmed ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/814222 Title: kvm cannot use vhd files over 127GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/814222/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 804593] Re: Many Safely remove icons on virtualized XPs
@Horacio, The bug report does not list your precise qemu version. A somewhat recent update to natty's qemu added the commit 505597e4476a6bc219d0ec1362b760d71cb4fdca: Ignore pci unplug requests for unpluggable devices (CVE-2011-1751). Can you retry with qemu-kvm 0.14.0+noroms-0ubuntu4.3 and let us know if you can still reproduce? Note, I tried to reproduce, but I only was able to hot-unplug the 'PCI ram controller', and unplugging it did not affect qemu-kvm. ** Changed in: qemu-kvm (Ubuntu) Status: New = Incomplete ** Changed in: qemu-kvm (Ubuntu) Importance: Low = High ** Changed in: qemu-kvm (Ubuntu) Importance: High = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/804593 Title: Many Safely remove icons on virtualized XPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/804593/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 804593] Re: Many Safely remove icons on virtualized XPs
(Changing to medium priority - there's not really a way to prevent this, but OTOH it only crashes the guest) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/804593 Title: Many Safely remove icons on virtualized XPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/804593/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524447] Re: virsh save is very slow
I'd like to help get this fixed, particularly in Lucid. What can I do? Does #21 and #22 still need testing? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/524447 Title: virsh save is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/524447/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
This fix has been committed in a kernel to proposed. Updating the status of the bug to reflect that. ** Changed in: linux (Ubuntu Lucid) Milestone: ubuntu-10.04.3 = lucid-updates ** Changed in: linux (Ubuntu Lucid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/588861 Title: pad block corrupted error when trying to register an image with 2.6.34 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/588861/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524447] Re: virsh save is very slow
@Jeff, they do still need testing. However at this point new ones need to be generated. There is a bit of a backlog on libvirt updates to push. Depending on how those go, I could get packages into -proposed either next week or in 2-3 weeks. I'll make a note to queue this, and ping here when I've pushed a fix to -proposed, asking you to test. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/524447 Title: virsh save is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/524447/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524447] Re: virsh save is very slow
Oops, this is for qemu-kvm, not libvirt. That can go immediately. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/524447 Title: virsh save is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/524447/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 791607] Re: Oneiric Eucalyptus fails to start up
** Changed in: eucalyptus (Ubuntu Oneiric) Assignee: (unassigned) = Ubuntu Server Team (ubuntu-server) -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/791607 Title: Oneiric Eucalyptus fails to start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/791607/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524447] Re: virsh save is very slow
(setting importance to medium because it has a moderate impact on a core application, and especially because it has no workaround) ** Changed in: qemu-kvm (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: qemu-kvm (Ubuntu Maverick) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/524447 Title: virsh save is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/524447/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524447] Re: virsh save is very slow
Ok, great! Thanks for the quick response. I did just now get finished testing the packages you attached in #21 using my lucid box. Saves of a 256Mb guest went from ~50 seconds to ~3. So it does seem to fix the issue. I can set up a Maverick box if you need it tested there as well. I checked for basic functionality with the packages you provided and the basics seem to work, (virsh start, stop, restore, save. Guest disk, net, vnc) but I didn't do much more. How deep should I go testing for regressions? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/524447 Title: virsh save is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/524447/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524447] Re: virsh save is very slow
Actually maverick is waiting for a fix for bug 790145 to be verified, but lucid is free. I've uploaded the proposed fix to lucid-proposed, it's waiting for an SRU admin to approve it. I will also post the amd64 lucid .debs at http://people.canonical.com/~serge/qemu-slow-save/. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/524447 Title: virsh save is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/524447/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
