[Bug 1050762] [NEW] obsolete config files of bind9 left after the oneiric 2 precise upgrade
You have been subscribed to a public bug: lucid to precise upgrade : server | main | universe arch: i386 | amd64 obsolete config file: bind9 /etc/bind/named.conf.options Link to the tests: https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job/precise-upgrade-oneiric-server/244/ https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job/precise-upgrade-oneiric-main/232/ https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job/precise-upgrade-oneiric-universe/233/ ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade oneiric2precise precise qa-daily-testing -- obsolete config files of bind9 left after the oneiric 2 precise upgrade https://bugs.launchpad.net/bugs/1050762 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. -- 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 1048787] Re: slapd gives assertions for valid configuration
** Changed in: openldap (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1048787 Title: slapd gives assertions for valid configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1048787/+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 1041829] Re: package bacula-director-mysql 5.2.5-0ubuntu6.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bacula (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1041829 Title: package bacula-director-mysql 5.2.5-0ubuntu6.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1041829/+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 1050719] [NEW] lxc.hook.* not working
Public bug reported: clear_config_item(lxc.hook) works, but clear_config_item(lxc.hook.pre- mount) does not. They should be implemented. ** Affects: lxc (Ubuntu) Importance: High Status: Triaged ** Changed in: lxc (Ubuntu) Status: New => Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1050719 Title: lxc.hook.* not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050719/+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 1050559] Re: Sync cyrus-sasl2 2.1.25.dfsg1-5 (main) from Debian unstable (main)
The documentation improvement and NEWS file are definitely Ubuntu- relevant. ** Changed in: cyrus-sasl2 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1050559 Title: Sync cyrus-sasl2 2.1.25.dfsg1-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1050559/+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 1031065] Re: cloud-init-nonet runs 'start networking' explicitly
** Branch linked: lp:~smoser/cloud-init/trunk.lp1031065 -- 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/1031065 Title: cloud-init-nonet runs 'start networking' explicitly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+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 1050663] Re: Weird key bindings in vi in an ssh session from 64bit to 32bit
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1050663 Title: Weird key bindings in vi in an ssh session from 64bit to 32bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1050663/+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 1050663] [NEW] Weird key bindings in vi in an ssh session from 64bit to 32bit
Public bug reported: I support a number of systems remotely, and often find myself using vi in an ssh session to edit various files. In some cases, but not all, when I press the up arrow (in insert mode) I get a capital letter A and a new line instead of the cursor moving up. Other arrow keys have similar issues. This only seems to be a problem when in insert mode. My system is 12.04 64 bit. When I connect to a remote system that is 64 bit it works fine, but when I connect to a remote 32 bit system, I have the described problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: openssh-client 1:5.9p1-5ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Thu Sep 13 18:12:18 2012 ExecutablePath: /usr/bin/ssh InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:5.9p1-5ubuntu1 SSHClientVersion: OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1050663 Title: Weird key bindings in vi in an ssh session from 64bit to 32bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1050663/+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 1050559] Re: Sync cyrus-sasl2 2.1.25.dfsg1-5 (main) from Debian unstable (main)
Hi Logan, would you mind summarizing what the Ubuntu-relevant fixes/changes are for this package, to make sponsoring easier? ** Changed in: cyrus-sasl2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1050559 Title: Sync cyrus-sasl2 2.1.25.dfsg1-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1050559/+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 1048075] Re: Error updating RRD file (extra data on update argument)
** Attachment added: "sensorsd logfile" https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1048075/+attachment/3313462/+files/sensord.rrd.xz ** Changed in: lm-sensors (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1048075 Title: Error updating RRD file (extra data on update argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1048075/+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 1036902] Re: Block storage connections are NOT restored on system reboot
** Also affects: nova/essex Importance: Undecided Status: New -- 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/1036902 Title: Block storage connections are NOT restored on system reboot To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1036902/+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 1048787] Re: slapd gives assertions for valid configuration
** Description changed: - The slapd version in Ubuntu precise (2.4.28-1.1ubuntu4.1) suffers from - the same issue that was reported in debian BTS for the debian version - 2.4.28-1.1. + [Impact] + + [Fix] + + [Test Case] + + [Regression Potential] + + [Original Report] + The slapd version in Ubuntu precise (2.4.28-1.1ubuntu4.1) suffers from the same issue that was reported in debian BTS for the debian version 2.4.28-1.1. When configuring the shell backend in slapd.conf the syntax is (see man slapd-shell): add ... bind ... compare ... and so on. That is the path to the script followed by its arguments. This has worked fine in the past. However, the current version 2.4.28-1.1 of the slapd server refuses to start if any arguments are given after the path name in the configuration file, with the following assertion: slapd: ../../../../servers/slapd/config.c:198: config_check_vals: Assertion `c->argc == 2' failed. For the configuration of the shell backend the assertion condition means that it is not possible to pass arguments to the script in the slapd.conf. The man pages documents that this should still be possible, and it has been working with earlier versions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1048787 Title: slapd gives assertions for valid configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1048787/+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 1044318] Re: [SRU] pre-1.5 OVS has trouble with floating ips when pinging from the same box
** Description changed: - Note: OVS from before 1.5, which includes the default versions shipped - with 12.04 and Fedora 17, has a bug that causes it not to work correctly - with floating IPs when the person contacting the floating IP is on the - same box as quantum-l3-agent. + [Impact] + The connection tracking logic using by IPtables gets confused if a packet passes through multiple linux network namespaces on the same host. The reason for this confusion is that OVS is not properly clearing some of the fields in the skb header, meaning the connection tracking ignores this packet, so iptables functionality that relies on this (in particular DNAT and SNAT) do not work. + + In particular, the use of OVS by OpenStack Quantum is critically + affected by this bug. + + [Fix] + The issue has been fixed upstream as of 1.4.3. A minimal 5-liner that clears the appropriate metadata from the skb header. The patch has been cherry-picked and fix released in the current Ubuntu dev. release (12.10). + + [Test Case] + 1. Create external network 40.0.0.0/24 for floating IPs + 2. Assign br-ex the IP 40.0.0.1 + 3. Pinging 40.0.0.1 appears to work, but you're pinging the router, not the VM + 4. Network connectivity to the VM with the floating IP does not work, as expected. + + [Regression Potential] + Minimal. Simple patch that has been cherry-picked from the current upstream stable release of Openvswitch (1.4.3). + + [Original Report] + Note: OVS from before 1.5, which includes the default versions shipped with 12.04 and Fedora 17, has a bug that causes it not to work correctly with floating IPs when the person contacting the floating IP is on the same box as quantum-l3-agent. While not very likely to happen in a production setup, this is fairly common in simple development environments. For example, let's say you create an external network 40.0.0.0/24 for floating IPs. If you then assign br-ex the IP 40.0.0.1, you should be able to reach all of your VMs with floating IPs, but it won't work because of this bug. Oddly, it - will often appear to work if you use ping, but in reality you are pining - the IP address in the router namespace, not the VM. + will often appear to work if you use ping, but in reality you are + pinging the IP address in the router namespace, not the VM. We believe the following OVS commit it required for this to work properly: http://openvswitch.org/cgi- bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=53e6421bc83918ac2d00ba5516f205fa7e394140 We are looking at creating a new stable release on the 1.4.x branch to include this change and plan to work with distros to get it pulled into their packages. - - [IMPACT] - The connection tracking logic using by IPtables gets confused if a packet passes through multiple linux network namespaces on the same host. The reason for this confusion is that OVS is not properly clearing some of the fields in the skb header, meaning the connection tracking ignores this packet, so iptables functionality that relies on this (in particular DNAT and SNAT) do not work. - - In particular, the use of OVS by OpenStack Quantum is critically - affected by this bug. - - [FIX] - The issue has been fixed upstream as of 1.4.3. A minimal 5-liner that clears the appropriate metadata from the skb header. The patch has been cherry-picked and fix released in the current Ubuntu dev. release (12.10). - - [REGRESSION POTENTIAL] - Minimal. Simple patch that has been cherry-picked from the currentl upstream stable release of Openvswitch (1.4.3). ** Changed in: openvswitch (Ubuntu Precise) Status: Confirmed => Triaged ** Changed in: openvswitch (Ubuntu Precise) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1044318 Title: [SRU] pre-1.5 OVS has trouble with floating ips when pinging from the same box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1044318/+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 1039542] Re: Please re-enable PIE and BIND_NOW
** Tags added: precise quantal -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu. https://bugs.launchpad.net/bugs/1039542 Title: Please re-enable PIE and BIND_NOW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1039542/+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 1050559] [NEW] Sync cyrus-sasl2 2.1.25.dfsg1-5 (main) from Debian unstable (main)
Public bug reported: Please sync cyrus-sasl2 2.1.25.dfsg1-5 (main) from Debian unstable (main) Changelog entries since current quantal version 2.1.25.dfsg1-4build1: cyrus-sasl2 (2.1.25.dfsg1-5) unstable; urgency=low * New sourceful upload (Closes: #676914) * Relabel /run directory for SE Linux (Closes: #677685) * Add a NEWS file about auxprop_plugin mysql->sql change (Closes: #680476) * Improve documentation on LDAP_SASLAUTHD file (Closes: #671015) -- Ondřej Surý Mon, 06 Aug 2012 13:34:27 +0200 ** Affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1050559 Title: Sync cyrus-sasl2 2.1.25.dfsg1-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1050559/+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 1044553] Re: 'password' setting broken by usergroup changes
** 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/1044553 Title: 'password' setting broken by usergroup changes To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1044553/+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 1044594] Re: Cloud-archive not loading types correctly
** 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/1044594 Title: Cloud-archive not loading types correctly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1044594/+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 1050523] Re: maas kernel cmdline must include iscsi_initiator
** Branch linked: lp:~smoser/maas/kernel-cmdline-cleanup ** Changed in: maas Status: New => In Progress ** Changed in: maas Importance: Undecided => High ** Changed in: maas Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1050523 Title: maas kernel cmdline must include iscsi_initiator To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1050523/+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 1050211] Re: (CVE-2012-4244) bind9: specially crafted resource record causes named to exit
We don't track security issues with launchpad bugs, we track them in the Ubuntu CVE tracker: http://people.canonical.com/~ubuntu-security/cve/ ** Changed in: bind9 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1050211 Title: (CVE-2012-4244) bind9: specially crafted resource record causes named to exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1050211/+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 1050523] [NEW] maas kernel cmdline must include iscsi_initiator
Public bug reported: An upgrade of open-iscsi in quantal has left our ephemeral images not booting, as 'iscsi_initiator' is now a required kernel argument. To be fair, it was previously documented as required, but worked without it. Now the initramfs will fail to initialize the iscsi device if it is not found. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: maas (not installed) ProcVersionSignature: User Name 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 17:21:11 2012 Ec2AMI: ami-014b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas Importance: Undecided Status: New ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images quantal ** Also affects: maas Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1050523 Title: maas kernel cmdline must include iscsi_initiator To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1050523/+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 1049914] Re: cannot use long form of '--name' to lxc-clone
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu34 --- lxc (0.8.0~rc1-4ubuntu34) quantal; urgency=low [ Serge Hallyn ] * 0214-give-pclose-errno: help debug pclose failures when lxc runs scripts. * 0215-lxc-clone-name-arg: fix incorrect checking for --name argument. (LP: #1049914) * 0216-hook-kmsg-to-console: link /dev/kmsg to /dev/console so init log messages can be seen. (LP: #1049926) * 0217-lxc-clone-fix-fstab: fix check for lxc.mount in lxc-clone (LP: #1049987) * 0218-api-shutdown-fix-doublestop: don't call c->stop() when already stopped (LP: #1050001) * Update lxc-start-container apparmor abstraction to allow ecryptfs mounts from the pre-mount script. Remove the instruction to add that line from the example hook. * Update lxc-start-container apparmor abstraction to allow mounts to paths under /var/lib/lxc/$container/, so that pre-mount hooks can stage mounts there. Also update the mountecryptfs example premount hook to use that. (LP: #1050469) * debian/rules: remove parsing of apparmor.in files. [ Stéphane Graber ] * Update lxc-start-container apparmor abstraction to allow aufs and overlayfs mounts from the pre-mount scripts. This is required by some hooks and will be needed by the new lxc-start-ephemeral. * Remove multi-arch path in lxc-start-container apparmor abstraction and instead just allow /usr/lib/*/lxc/ so nested containers running on a different architecture don't get blocked by apparmor. * Cherry-pick python-lxc fixes from upstream: - Minor PEP-8 syntax fix - Return an exception when getting Container instance as non-root - Automatically convert any state string passed to wait() to its uppercase equivalent. - Replace test.py by a full example of the API. - Remove zombie handler function from C module as it's no longer required and causes weird bugs when used with the hooks. [ William Grant ] * lxc-start-ephemeral: exit with the command's status, not always 0. (LP: #1050351) -- Serge HallynThu, 13 Sep 2012 12:02:45 -0500 ** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1049914 Title: cannot use long form of '--name' to lxc-clone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1049914/+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 1049926] Re: logging of init doesn't go to console
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu34 --- lxc (0.8.0~rc1-4ubuntu34) quantal; urgency=low [ Serge Hallyn ] * 0214-give-pclose-errno: help debug pclose failures when lxc runs scripts. * 0215-lxc-clone-name-arg: fix incorrect checking for --name argument. (LP: #1049914) * 0216-hook-kmsg-to-console: link /dev/kmsg to /dev/console so init log messages can be seen. (LP: #1049926) * 0217-lxc-clone-fix-fstab: fix check for lxc.mount in lxc-clone (LP: #1049987) * 0218-api-shutdown-fix-doublestop: don't call c->stop() when already stopped (LP: #1050001) * Update lxc-start-container apparmor abstraction to allow ecryptfs mounts from the pre-mount script. Remove the instruction to add that line from the example hook. * Update lxc-start-container apparmor abstraction to allow mounts to paths under /var/lib/lxc/$container/, so that pre-mount hooks can stage mounts there. Also update the mountecryptfs example premount hook to use that. (LP: #1050469) * debian/rules: remove parsing of apparmor.in files. [ Stéphane Graber ] * Update lxc-start-container apparmor abstraction to allow aufs and overlayfs mounts from the pre-mount scripts. This is required by some hooks and will be needed by the new lxc-start-ephemeral. * Remove multi-arch path in lxc-start-container apparmor abstraction and instead just allow /usr/lib/*/lxc/ so nested containers running on a different architecture don't get blocked by apparmor. * Cherry-pick python-lxc fixes from upstream: - Minor PEP-8 syntax fix - Return an exception when getting Container instance as non-root - Automatically convert any state string passed to wait() to its uppercase equivalent. - Replace test.py by a full example of the API. - Remove zombie handler function from C module as it's no longer required and causes weird bugs when used with the hooks. [ William Grant ] * lxc-start-ephemeral: exit with the command's status, not always 0. (LP: #1050351) -- Serge HallynThu, 13 Sep 2012 12:02:45 -0500 ** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1049926 Title: logging of init doesn't go to console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1049926/+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 1049987] Re: lxc-cloned container breaks if source is later destroyed
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu34 --- lxc (0.8.0~rc1-4ubuntu34) quantal; urgency=low [ Serge Hallyn ] * 0214-give-pclose-errno: help debug pclose failures when lxc runs scripts. * 0215-lxc-clone-name-arg: fix incorrect checking for --name argument. (LP: #1049914) * 0216-hook-kmsg-to-console: link /dev/kmsg to /dev/console so init log messages can be seen. (LP: #1049926) * 0217-lxc-clone-fix-fstab: fix check for lxc.mount in lxc-clone (LP: #1049987) * 0218-api-shutdown-fix-doublestop: don't call c->stop() when already stopped (LP: #1050001) * Update lxc-start-container apparmor abstraction to allow ecryptfs mounts from the pre-mount script. Remove the instruction to add that line from the example hook. * Update lxc-start-container apparmor abstraction to allow mounts to paths under /var/lib/lxc/$container/, so that pre-mount hooks can stage mounts there. Also update the mountecryptfs example premount hook to use that. (LP: #1050469) * debian/rules: remove parsing of apparmor.in files. [ Stéphane Graber ] * Update lxc-start-container apparmor abstraction to allow aufs and overlayfs mounts from the pre-mount scripts. This is required by some hooks and will be needed by the new lxc-start-ephemeral. * Remove multi-arch path in lxc-start-container apparmor abstraction and instead just allow /usr/lib/*/lxc/ so nested containers running on a different architecture don't get blocked by apparmor. * Cherry-pick python-lxc fixes from upstream: - Minor PEP-8 syntax fix - Return an exception when getting Container instance as non-root - Automatically convert any state string passed to wait() to its uppercase equivalent. - Replace test.py by a full example of the API. - Remove zombie handler function from C module as it's no longer required and causes weird bugs when used with the hooks. [ William Grant ] * lxc-start-ephemeral: exit with the command's status, not always 0. (LP: #1050351) -- Serge HallynThu, 13 Sep 2012 12:02:45 -0500 ** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1049987 Title: lxc-cloned container breaks if source is later destroyed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1049987/+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 1050001] Re: API shutdown(timeout=X) call always tries to call stop(), spewing error messages to the console when the container is already stopped
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu34 --- lxc (0.8.0~rc1-4ubuntu34) quantal; urgency=low [ Serge Hallyn ] * 0214-give-pclose-errno: help debug pclose failures when lxc runs scripts. * 0215-lxc-clone-name-arg: fix incorrect checking for --name argument. (LP: #1049914) * 0216-hook-kmsg-to-console: link /dev/kmsg to /dev/console so init log messages can be seen. (LP: #1049926) * 0217-lxc-clone-fix-fstab: fix check for lxc.mount in lxc-clone (LP: #1049987) * 0218-api-shutdown-fix-doublestop: don't call c->stop() when already stopped (LP: #1050001) * Update lxc-start-container apparmor abstraction to allow ecryptfs mounts from the pre-mount script. Remove the instruction to add that line from the example hook. * Update lxc-start-container apparmor abstraction to allow mounts to paths under /var/lib/lxc/$container/, so that pre-mount hooks can stage mounts there. Also update the mountecryptfs example premount hook to use that. (LP: #1050469) * debian/rules: remove parsing of apparmor.in files. [ Stéphane Graber ] * Update lxc-start-container apparmor abstraction to allow aufs and overlayfs mounts from the pre-mount scripts. This is required by some hooks and will be needed by the new lxc-start-ephemeral. * Remove multi-arch path in lxc-start-container apparmor abstraction and instead just allow /usr/lib/*/lxc/ so nested containers running on a different architecture don't get blocked by apparmor. * Cherry-pick python-lxc fixes from upstream: - Minor PEP-8 syntax fix - Return an exception when getting Container instance as non-root - Automatically convert any state string passed to wait() to its uppercase equivalent. - Replace test.py by a full example of the API. - Remove zombie handler function from C module as it's no longer required and causes weird bugs when used with the hooks. [ William Grant ] * lxc-start-ephemeral: exit with the command's status, not always 0. (LP: #1050351) -- Serge HallynThu, 13 Sep 2012 12:02:45 -0500 ** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1050001 Title: API shutdown(timeout=X) call always tries to call stop(), spewing error messages to the console when the container is already stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050001/+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 1050351] Re: lxc-start-ephemeral suppresses command exit status
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu34 --- lxc (0.8.0~rc1-4ubuntu34) quantal; urgency=low [ Serge Hallyn ] * 0214-give-pclose-errno: help debug pclose failures when lxc runs scripts. * 0215-lxc-clone-name-arg: fix incorrect checking for --name argument. (LP: #1049914) * 0216-hook-kmsg-to-console: link /dev/kmsg to /dev/console so init log messages can be seen. (LP: #1049926) * 0217-lxc-clone-fix-fstab: fix check for lxc.mount in lxc-clone (LP: #1049987) * 0218-api-shutdown-fix-doublestop: don't call c->stop() when already stopped (LP: #1050001) * Update lxc-start-container apparmor abstraction to allow ecryptfs mounts from the pre-mount script. Remove the instruction to add that line from the example hook. * Update lxc-start-container apparmor abstraction to allow mounts to paths under /var/lib/lxc/$container/, so that pre-mount hooks can stage mounts there. Also update the mountecryptfs example premount hook to use that. (LP: #1050469) * debian/rules: remove parsing of apparmor.in files. [ Stéphane Graber ] * Update lxc-start-container apparmor abstraction to allow aufs and overlayfs mounts from the pre-mount scripts. This is required by some hooks and will be needed by the new lxc-start-ephemeral. * Remove multi-arch path in lxc-start-container apparmor abstraction and instead just allow /usr/lib/*/lxc/ so nested containers running on a different architecture don't get blocked by apparmor. * Cherry-pick python-lxc fixes from upstream: - Minor PEP-8 syntax fix - Return an exception when getting Container instance as non-root - Automatically convert any state string passed to wait() to its uppercase equivalent. - Replace test.py by a full example of the API. - Remove zombie handler function from C module as it's no longer required and causes weird bugs when used with the hooks. [ William Grant ] * lxc-start-ephemeral: exit with the command's status, not always 0. (LP: #1050351) -- Serge HallynThu, 13 Sep 2012 12:02:45 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1050351 Title: lxc-start-ephemeral suppresses command exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050351/+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 1050469] Re: cannot use more than one ecryptfs container
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu34 --- lxc (0.8.0~rc1-4ubuntu34) quantal; urgency=low [ Serge Hallyn ] * 0214-give-pclose-errno: help debug pclose failures when lxc runs scripts. * 0215-lxc-clone-name-arg: fix incorrect checking for --name argument. (LP: #1049914) * 0216-hook-kmsg-to-console: link /dev/kmsg to /dev/console so init log messages can be seen. (LP: #1049926) * 0217-lxc-clone-fix-fstab: fix check for lxc.mount in lxc-clone (LP: #1049987) * 0218-api-shutdown-fix-doublestop: don't call c->stop() when already stopped (LP: #1050001) * Update lxc-start-container apparmor abstraction to allow ecryptfs mounts from the pre-mount script. Remove the instruction to add that line from the example hook. * Update lxc-start-container apparmor abstraction to allow mounts to paths under /var/lib/lxc/$container/, so that pre-mount hooks can stage mounts there. Also update the mountecryptfs example premount hook to use that. (LP: #1050469) * debian/rules: remove parsing of apparmor.in files. [ Stéphane Graber ] * Update lxc-start-container apparmor abstraction to allow aufs and overlayfs mounts from the pre-mount scripts. This is required by some hooks and will be needed by the new lxc-start-ephemeral. * Remove multi-arch path in lxc-start-container apparmor abstraction and instead just allow /usr/lib/*/lxc/ so nested containers running on a different architecture don't get blocked by apparmor. * Cherry-pick python-lxc fixes from upstream: - Minor PEP-8 syntax fix - Return an exception when getting Container instance as non-root - Automatically convert any state string passed to wait() to its uppercase equivalent. - Replace test.py by a full example of the API. - Remove zombie handler function from C module as it's no longer required and causes weird bugs when used with the hooks. [ William Grant ] * lxc-start-ephemeral: exit with the command's status, not always 0. (LP: #1050351) -- Serge HallynThu, 13 Sep 2012 12:02:45 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1050469 Title: cannot use more than one ecryptfs container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050469/+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 1050459] Re: Dependency typo (python-urrlib3 instead of python-urllib3)
This was fixed in version 0.12.1-1ubuntu6 in Quantal. ** Changed in: requests (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to requests in Ubuntu. https://bugs.launchpad.net/bugs/1050459 Title: Dependency typo (python-urrlib3 instead of python-urllib3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/requests/+bug/1050459/+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
[Blueprint servercloud-q-openstack-stable] OpenStack SRUs
Blueprint changed by Chuck Short: Work items changed: Work items: - [zulcss] Formalize Openstack SRU policy for Precise: INPROGRESS + [zulcss] Formalize Openstack SRU policy for Precise: DONE [zulcss] Prepare ubuntu packaging branches for stable: DONE [zulcss] Prepare upstream tarballs for essex/stable branches: DONE [zulcss] Prepare openstack-ci for testing of essex/stable: DONE [zulcss] Week 5 Monitor relevant projects for apprioate fixes: DONE [zulcss] Week 6 prepare for openstack SRU (prepare packaging): DONE Week 7 call for testing for openstack SRU (upload): DONE Week 8 finalize openstack SRU (internal/external testing): DONE Week 10 Monitor relevant projects for apprioate fixes: DONE Week 11 prepare for openstack SRU (prepare packaging): DONE Week 12 call for testing for openstack SRU (upload): DONE Week 13 finalize openstack SRU (internal/external testing): DONE Week 15 Monitor relevant projects for apporiate fixes: TODO Week 16 prepare for openstack SRU (prepare packaging): TODO Week 17 call for testing for openstack SRU (upload): TODO Week 18 finalize openstack SRU (internal/external testing): TODO Apply for standing micro-release for openstack to SRU: DONE -- OpenStack SRUs https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-openstack-stable -- 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
[Blueprint servercloud-q-openstack-stable] OpenStack SRUs
Blueprint changed by Chuck Short: Work items changed: Work items: [zulcss] Formalize Openstack SRU policy for Precise: INPROGRESS [zulcss] Prepare ubuntu packaging branches for stable: DONE [zulcss] Prepare upstream tarballs for essex/stable branches: DONE [zulcss] Prepare openstack-ci for testing of essex/stable: DONE [zulcss] Week 5 Monitor relevant projects for apprioate fixes: DONE [zulcss] Week 6 prepare for openstack SRU (prepare packaging): DONE Week 7 call for testing for openstack SRU (upload): DONE Week 8 finalize openstack SRU (internal/external testing): DONE - Week 10 Monitor relevant projects for apprioate fixes: TODO - Week 11 prepare for openstack SRU (prepare packaging): TODO - Week 12 call for testing for openstack SRU (upload): TODO - Week 13 finalize openstack SRU (internal/external testing): TODO + Week 10 Monitor relevant projects for apprioate fixes: DONE + Week 11 prepare for openstack SRU (prepare packaging): DONE + Week 12 call for testing for openstack SRU (upload): DONE + Week 13 finalize openstack SRU (internal/external testing): DONE Week 15 Monitor relevant projects for apporiate fixes: TODO Week 16 prepare for openstack SRU (prepare packaging): TODO Week 17 call for testing for openstack SRU (upload): TODO Week 18 finalize openstack SRU (internal/external testing): TODO - Apply for standing micro-release for openstack to SRU: TODO + Apply for standing micro-release for openstack to SRU: DONE -- OpenStack SRUs https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-openstack-stable -- 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
[Blueprint servercloud-q-cloud-archive] Ubuntu Cloud Archive
Blueprint changed by Chuck Short: Work items changed: Work items: Write up policy for cloud archive: DONE Write up process for cloud archvie: DONE Create related packaging branches: DONE - Write upgrade tests for Openstack: TODO + Write upgrade tests for Openstack: INPROGRESS Create openstack-ci infrastructure: DONE Liase with canonical-is to create cloud-archive for precise-folsom: DONE Create launchpad project for cloud-archvie: DONE Create staging PPA for cloud-archive: DONE Publicize cloud-archive in a blog post: TODO Upload folsom-1 to the cloud archive: DONE Upload folsom-2 to the cloud archive: DONE Upload folsom-3 to the cloud archive: DONE - Upload release candidate to the cloud archive: TODO + Upload release candidate to the cloud archive: INPROGRESS Upload final release to the cloud archive: TODO -- Ubuntu Cloud Archive https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-cloud-archive -- 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 1050469] [NEW] cannot use more than one ecryptfs container
Public bug reported: The instructions in the example ecryptfs hook place the ecryptfs mount in /var/lib/lxc/ecryptfs_root. This causes a /var/lib/lxc/ectyprfs_root.hold file to be created at container start, preventing the simultaneous use of >1 encrypted container. Fix the instructions and the hook, and add permission for lxc-start to mount under /var/lib/lxc/** ** Affects: lxc (Ubuntu) Importance: High Assignee: Serge Hallyn (serge-hallyn) Status: In Progress ** Description changed: The instructions in the example ecryptfs hook place the ecryptfs mount in /var/lib/lxc/ecryptfs_root. This causes a /var/lib/lxc/ectyprfs_root.hold file to be created at container start, preventing the simultaneous use of >1 encrypted container. - Fix the instructions and the hook. + Fix the instructions and the hook, and add permission for lxc-start to + mount under /var/lib/lxc/** ** Changed in: lxc (Ubuntu) Importance: Undecided => High ** Changed in: lxc (Ubuntu) Status: New => In Progress ** Changed in: lxc (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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1050469 Title: cannot use more than one ecryptfs container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050469/+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 1005951] Re: lxc-fedora template is broken with fedora 17
@Dan, Is what is in comment #2 enoug to fix the bug for you? If not, do you mind preparing a full diff? I'll go ahead and apply it then. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1005951 Title: lxc-fedora template is broken with fedora 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1005951/+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 1050001] Re: API shutdown(timeout=X) call always tries to call stop(), spewing error messages to the console when the container is already stopped
@stgraber,
heh, obviously I meant to pull that from the cut-paste :)
** Description changed:
Title should say it all, example is available at:
http://paste.ubuntu.com/1201056/
18:45 d'oh. i think i line got dropped there
18:46 the if (timeout > 0) should be if (!retv && timeout > 0)
18:46 we're calling c->stop() on a stopped container otherwise
The test case is:
root@amd1:~/bzr/lxc/lxc# python3
- Python 3.2.3 (default, Sep 10 2012, 12:07:24)
+ Python 3.2.3 (default, Sep 10 2012, 12:07:24)
[GCC 4.7.1 20120908 (prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import lxc
__main__:1: Warning: The python-lxc API isn't yet stable and may change at
any point in the future.
>>> c=lxc.Container("qlvm3")
>>> c.start()
True
- >>> c.stop(timeout=5)
- Traceback (most recent call last):
- File "", line 1, in
- TypeError: stop() takes no keyword arguments
>>> c.shutdown(timeout=5)
lxc_container: failed to receive answer for the command
lxc_container: failed to send command
True
>>>
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1050001
Title:
API shutdown(timeout=X) call always tries to call stop(), spewing
error messages to the console when the container is already stopped
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050001/+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 1050001] Re: API shutdown(timeout=X) call always tries to call stop(), spewing error messages to the console when the container is already stopped
Right, except that you probably should have called stop() instead of stop(timeout=X) as stop doesn't take a timeout, but anyway, the relevant part is the messages printed by shutdown(). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1050001 Title: API shutdown(timeout=X) call always tries to call stop(), spewing error messages to the console when the container is already stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050001/+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 1050001] Re: API shutdown(timeout=X) call always tries to call stop(), spewing error messages to the console when the container is already stopped
** Description changed:
Title should say it all, example is available at:
http://paste.ubuntu.com/1201056/
18:45 d'oh. i think i line got dropped there
18:46 the if (timeout > 0) should be if (!retv && timeout > 0)
18:46 we're calling c->stop() on a stopped container otherwise
+
+ The test case is:
+
+ root@amd1:~/bzr/lxc/lxc# python3
+ Python 3.2.3 (default, Sep 10 2012, 12:07:24)
+ [GCC 4.7.1 20120908 (prerelease)] on linux2
+ Type "help", "copyright", "credits" or "license" for more information.
+ >>> import lxc
+ __main__:1: Warning: The python-lxc API isn't yet stable and may change at
any point in the future.
+ >>> c=lxc.Container("qlvm3")
+ >>> c.start()
+ True
+ >>> c.stop(timeout=5)
+ Traceback (most recent call last):
+ File "", line 1, in
+ TypeError: stop() takes no keyword arguments
+ >>> c.shutdown(timeout=5)
+ lxc_container: failed to receive answer for the command
+ lxc_container: failed to send command
+ True
+ >>>
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1050001
Title:
API shutdown(timeout=X) call always tries to call stop(), spewing
error messages to the console when the container is already stopped
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050001/+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 1049987] Re: lxc-cloned container breaks if source is later destroyed
** Changed in: lxc (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1049987 Title: lxc-cloned container breaks if source is later destroyed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1049987/+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 1047059] Re: Packaging Issues into Ubuntu 12.04
** No longer affects: cinder -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1047059 Title: Packaging Issues into Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1047059/+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 1045438] Re: Impossible to run cinder-volume from folsom testing packages or archive
** No longer affects: cinder -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1045438 Title: Impossible to run cinder-volume from folsom testing packages or archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1045438/+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 1040682] Re: [MIR] ipmitool
I would explore the option of making a primary alternative depends of freeipmi-tools. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1040682 Title: [MIR] ipmitool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1040682/+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 1048864] Re: Latest python in quantal breaks juju
** Summary changed: - Latest python in quantal breaks juju test suite + Latest python in quantal breaks juju -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1048864 Title: Latest python in quantal breaks juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1048864/+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 1050351] Re: lxc-start-ephemeral suppresses command exit status
** Branch linked: lp:~wgrant/ubuntu/quantal/lxc/bug-1050351 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1050351 Title: lxc-start-ephemeral suppresses command exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050351/+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 1050351] Re: lxc-start-ephemeral suppresses command exit status
** Branch linked: lp:~wgrant/ubuntu/precise/lxc/bug-1050351 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1050351 Title: lxc-start-ephemeral suppresses command exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050351/+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 1050351] [NEW] lxc-start-ephemeral suppresses command exit status
Public bug reported: lxc-start-ephemeral supports executing a command directly, but always exits 0 rather than using the command's status, causing errors to go unnoticed when used programmatically. ** Affects: lxc (Ubuntu) Importance: Low Assignee: William Grant (wgrant) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1050351 Title: lxc-start-ephemeral suppresses command exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050351/+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 990751] Re: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Since my update to precise slapd has this bug. Purging and reinstalling doesn't
help. So I run slapd -Tt and got this:
sudo slapd -Tt
[sudo] password for martin:
5051b004 olcDbDirectory: value #0: invalid path: Permission denied
5051b004 config error processing olcDatabase={1}hdb,cn=config: olcDbDirectory:
value #0: invalid path: Permission denied
slaptest: bad configuration file!
I hope this helps.
Ubuntu 32bit on AMD64 system
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/990751
Title:
package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned
error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/990751/+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
