Re: [Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
On 2012-01-24T02:24:39-, Tel li...@lnx-bsp.net wrote: Agree that the IO Service time is made somewhat redundant by the Disk Latency graph which shows much the same information. However, IO Service time itemises read and write, and after coming this far, seems a shame not to make the small fix to get it working properly. Actually, the diskstats plugin does itemize read and write, per device, if you click on the top-level graph. So iostat_ios does truly seem redundant, while producing graphs that don't look as nice and aren't per-device. -- Kenyon Ralph -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+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 960713] Re: more debian/control issues
This bug was fixed in the package quantum - 2012.1~rc1-0ubuntu3 --- quantum (2012.1~rc1-0ubuntu3) precise; urgency=low * debian/control: Fix spelling typos. (LP: #960713) -- Paolo Rotolo paolorot...@ubuntu-it.org Fri, 23 Mar 2012 21:35:54 +0100 ** Changed in: quantum (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quantum in Ubuntu. https://bugs.launchpad.net/bugs/960713 Title: more debian/control issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quantum/+bug/960713/+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 959426] Re: nova + glance services die if started before db is reachable
** Changed in: nova Assignee: (unassigned) = Adam Gandelman (gandelman-a) -- 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/959426 Title: nova + glance services die if started before db is reachable To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/959426/+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 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Come on, a fix can't be done for this 4 years on? With all the various workarounds people have put in above comments, surely one of them can work for everyone?! -- 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/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/211631/+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 781949] Re: Must check certificates for validity
** Branch linked: lp:~clint-fewbar/juju/add-ssl-cert-verification -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to txaws in Ubuntu. https://bugs.launchpad.net/bugs/781949 Title: Must check certificates for validity To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/781949/+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 781949] Re: Must check certificates for validity
** Branch linked: lp:ubuntu/txaws -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to txaws in Ubuntu. https://bugs.launchpad.net/bugs/781949 Title: Must check certificates for validity To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/781949/+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 967037] [NEW] package samba-common 2:3.4.7~dfsg-1ubuntu3.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 10.04 Package: samba-common 2:3.4.7~dfsg-1ubuntu3.8 ProcVersionSignature: Ubuntu 2.6.32-40.87-generic 2.6.32.57+drm33.23 Uname: Linux 2.6.32-40-generic x86_64 Architecture: amd64 BothFailedConnect: Yes Date: Tue Mar 27 13:53:39 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release amd64 (20110720.1) PackageArchitecture: all SambaServerRegression: Yes SourcePackage: samba Title: package samba-common 2:3.4.7~dfsg-1ubuntu3.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- 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/967037 Title: package samba-common 2:3.4.7~dfsg-1ubuntu3.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967037/+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 967037] Re: package samba-common 2:3.4.7~dfsg-1ubuntu3.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 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/967037 Title: package samba-common 2:3.4.7~dfsg-1ubuntu3.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967037/+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 956366] Re: self-referential security groups can not be deleted
** Changed in: nova Milestone: essex-rc1 = essex-rc2 -- 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/956366 Title: self-referential security groups can not be deleted To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/956366/+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 967082] [NEW] package rabbitmq-erlang-client 2.7.1-0ubuntu3 failed to install/upgrade: subprocess new post-removal script returned error exit status 1
Public bug reported: I address this issue with an apt-get update then fixed the broken package. This issue was probably caused by Launchpad's own rabbitmq dependencies which uses non-standard packages, ProblemType: Package DistroRelease: Ubuntu 12.04 Package: rabbitmq-erlang-client 2.7.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 08:08:01 2012 ErrorMessage: subprocess new post-removal script returned error exit status 1 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: rabbitmq-server Title: package rabbitmq-erlang-client 2.7.1-0ubuntu3 failed to install/upgrade: subprocess new post-removal script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-01-15 (72 days ago) ** Affects: rabbitmq-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rabbitmq-server in Ubuntu. https://bugs.launchpad.net/bugs/967082 Title: package rabbitmq-erlang-client 2.7.1-0ubuntu3 failed to install/upgrade: subprocess new post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/967082/+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 967082] Re: package rabbitmq-erlang-client 2.7.1-0ubuntu3 failed to install/upgrade: subprocess new post-removal script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rabbitmq-server in Ubuntu. https://bugs.launchpad.net/bugs/967082 Title: package rabbitmq-erlang-client 2.7.1-0ubuntu3 failed to install/upgrade: subprocess new post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/967082/+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 956366] Re: self-referential security groups can not be deleted
Reviewed: https://review.openstack.org/5881 Committed: http://github.com/openstack/nova/commit/fd0ea778b0fd5932f1ca22de57cb6c872ed5b58f Submitter: Jenkins Branch:milestone-proposed commit fd0ea778b0fd5932f1ca22de57cb6c872ed5b58f Author: Mark McLoughlin mar...@redhat.com Date: Thu Mar 15 22:52:49 2012 -0400 Re-instate security group delete test case While fixing lp#956366, we realized that it's fine to delete a security group referenced by an ingress rule of another security group because the ingress rule gets deleted. Re-instate the test for this specific case, but test that the ingress rule gets deleted rather than an exception being thrown. Change-Id: I81ad16431f5f8f13561dfcb320213366e1e8864e ** Changed in: nova Status: Fix Committed = Fix Released -- 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/956366 Title: self-referential security groups can not be deleted To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/956366/+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 967082] Re: package rabbitmq-erlang-client 2.7.1-0ubuntu3 failed to install/upgrade: subprocess new post-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rabbitmq-server in Ubuntu. https://bugs.launchpad.net/bugs/967082 Title: package rabbitmq-erlang-client 2.7.1-0ubuntu3 failed to install/upgrade: subprocess new post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/967082/+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 781949] Re: Must check certificates for validity
This bug was fixed in the package txaws - 0.2-0ubuntu10 --- txaws (0.2-0ubuntu10) precise; urgency=low * d/patches/add-ssl-cert-verification.patch: Cherry pick patch from upstream to enable SSL certificate verification. (LP: #781949) -- Clint Byrum cl...@ubuntu.com Wed, 28 Mar 2012 02:39:34 -0700 ** Changed in: txaws (Ubuntu Precise) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to txaws in Ubuntu. https://bugs.launchpad.net/bugs/781949 Title: Must check certificates for validity To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/781949/+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 924337] Re: lxc on precise is not working with lucid containers (container does not reach runlevel 2)
This happens to me on a Natty container: salgado@delgadito:~$ cat /var/lib/lxc/patchmetrics/rootfs/etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=11.04 DISTRIB_CODENAME=natty DISTRIB_DESCRIPTION=Ubuntu 11.04 salgado@delgadito:~$ sudo lxc-start -n patchmetrics init: procps main process (26) terminated with status 255 init: udev-fallback-graphics main process (46) terminated with status 1 init: plymouth main process (6) killed by ABRT signal init: plymouth-splash main process (52) terminated with status 2 ** Changed in: lxc (Ubuntu Natty) Status: Invalid = Confirmed -- 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/924337 Title: lxc on precise is not working with lucid containers (container does not reach runlevel 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+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 959352] Re: Ephemeral containers have /rootfs prefix in /proc/self/maps entries
apport information ** Tags added: apport-collected precise staging ** Description changed: Ephemeral containers (but not non-ephemeral ones) have all of their /proc/*/maps entries prefixed with /rootfs. One problem this causes is that graphviz uses /proc/self/maps to locate its plugins. That means that some of the plugins can not be loaded. To reproduce the problem with dot, run this command: dot -Tcmapx /dev/null No output is expected, however because of the bug this output is produced: Format: cmapx not recognized. Use one of: dia hpgl mif mp pcl pic vtx A workaround for the problem with graphviz is to make the plugins available at the path it is expecting: mkdir -p /rootfs/usr/lib ln -s /usr/lib/graphviz /rootfs/usr/lib/graphviz + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. + ApportVersion: 1.95-0ubuntu1 + Architecture: i386 + DistroRelease: Ubuntu 12.04 + HibernationDevice: RESUME=UUID=2c5f282a-e713-4ae0-a940-87a40efd050f + InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) + MachineType: LENOVO 4313CTO + Package: lxc + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=8469c78f-d0fc-4564-a009-eed59bd1fdff ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + StagingDrivers: mei + Tags: precise staging + Uname: Linux 3.2.0-20-generic-pae i686 + UpgradeStatus: Upgraded to precise on 2012-01-24 (63 days ago) + UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare + dmi.bios.date: 10/26/2010 + dmi.bios.vendor: LENOVO + dmi.bios.version: 6MET81WW (1.41 ) + dmi.board.name: 4313CTO + dmi.board.vendor: LENOVO + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvr6MET81WW(1.41):bd10/26/2010:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 4313CTO + dmi.product.version: ThinkPad T510 + dmi.sys.vendor: LENOVO ** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955072/+files/AcpiTables.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955073/+files/AlsaDevices.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955074/+files/AplayDevices.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] ArecordDevices.txt
apport information ** Attachment added: ArecordDevices.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955075/+files/ArecordDevices.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] AudioDevicesInUse.txt
apport information ** Attachment added: AudioDevicesInUse.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955076/+files/AudioDevicesInUse.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955077/+files/BootDmesg.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955078/+files/CRDA.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Card0.Amixer.info.txt
apport information ** Attachment added: Card0.Amixer.info.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955079/+files/Card0.Amixer.info.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955080/+files/Card0.Amixer.values.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Card1.Amixer.info.txt
apport information ** Attachment added: Card1.Amixer.info.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955083/+files/Card1.Amixer.info.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Card29.Amixer.values.txt
apport information ** Attachment added: Card29.Amixer.values.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955086/+files/Card29.Amixer.values.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955089/+files/Lspci.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955081/+files/Card0.Codecs.codec.0.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Card0.Codecs.codec.3.txt
apport information ** Attachment added: Card0.Codecs.codec.3.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955082/+files/Card0.Codecs.codec.3.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Card1.Amixer.values.txt
apport information ** Attachment added: Card1.Amixer.values.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955084/+files/Card1.Amixer.values.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955087/+files/CurrentDmesg.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955088/+files/IwConfig.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955091/+files/PciMultimedia.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955090/+files/Lsusb.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] Card29.Amixer.info.txt
apport information ** Attachment added: Card29.Amixer.info.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955085/+files/Card29.Amixer.info.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955094/+files/ProcInterrupts.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955098/+files/UdevDb.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955100/+files/WifiSyslog.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955097/+files/RelatedPackageVersions.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955099/+files/UdevLog.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955092/+files/ProcCpuinfo.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955093/+files/ProcEnviron.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955095/+files/ProcModules.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 959352] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/959352/+attachment/2955096/+files/PulseList.txt -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 925024] Re: apparmor makes it impossible to install postgresql-common on Precise
I'm still seeing this issue; oneiric lxc container on latest precise kernel: Selecting previously deselected package ssl-cert. Unpacking ssl-cert (from .../ssl-cert_1.0.28_all.deb) ... Selecting previously deselected package postgresql-common. Unpacking postgresql-common (from .../postgresql-common_122ubuntu1_all.deb) ... Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by postgresql-common' dpkg: unrecoverable fatal error, aborting: failed to fstat previous diversions file: No such file or directory E: Sub-process /usr/bin/dpkg returned an error code (2) -- 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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 959352] Re: Ephemeral containers have /rootfs prefix in /proc/self/maps entries
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 967235] Re: smbd crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 956805 *** https://bugs.launchpad.net/bugs/956805 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #956805, so 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. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/967235/+attachment/2955518/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/967235/+attachment/2955520/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/967235/+attachment/2955521/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/967235/+attachment/2955522/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/967235/+attachment/2955523/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/967235/+attachment/2955524/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/967235/+attachment/2955526/+files/ThreadStacktrace.txt ** Visibility changed to: Public ** This bug has been marked a duplicate of private bug 956805 ** Visibility changed to: Public ** Tags removed: need-amd64-retrace -- 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/967235 Title: smbd crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967235/+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 959426] Fix proposed to glance (milestone-proposed)
Fix proposed to branch: milestone-proposed Review: https://review.openstack.org/5911 -- 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/959426 Title: nova + glance services die if started before db is reachable To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/959426/+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-p-juju-charm-testing] Juju: automated testing of charms
Blueprint changed by Clint Byrum: Whiteboard changed: Status: Spec nearing final approval. Merge proposals submitted against juju to implement some parts of the wrapper inside juju itself: http://pad.lv/939932 , http://pad.lv/939944 Work Items: [clint-fewbar] write spec for charm testing facility: DONE implement specified testing framework: INPROGRESS - deploy testing framework for use with local provider: TODO + [mark-mims] deploy testing framework for use with local provider (all phase1 tests are done w/ local provider): DONE deploy testing framework for use against ec2: TODO deploy testing framework for use against canonistack: TODO - deploy testing framework for use against orchestra (managing VMs instead of machines): TODO - write charm tests for mysql: TODO - [clint-fewbar] write charm tests for haproxy: TODO - [clint-fewbar] write charm tests for wordpress: TODO - [mark-mims] write charm tests for hadoop: TODO + deploy testing framework for use against orchestra (managing VMs instead of machines): POSTPONED + write charm tests for mysql: POSTPONED + [clint-fewbar] write charm tests for haproxy: POSTPONED + [clint-fewbar] write charm tests for wordpress: POSTPONED + [mark-mims] write charm tests for hadoop: POSTPONED [james-page] add openstack tests: TODO [mark-mims] jenkins charm to spawn basic charm tests: DONE [mark-mims] basic charm tests... just test install hooks for now: DONE Session notes: Welcome to Ubuntu Developer Summit! #uds-p #track #topic put your session notes here Requirements of automated testing of charms: * LET'S KEEP IT SIMPLE! :-) * Detect breakage of a charm relating to an interface * Identification of individual change which breaks a given relationship * Maybe implement tests that mock a relation to ensure implementers are compliant * Test dependent charms when a provider charm changes * Run test NxN of providers and requirers so all permutations are sane (_very_ expensive, probably impossible) * Run testing against multiple environment providers (EC2/OpenStack/BareMetal) * Notify maintainers when the charm breaks, rather than waiting for polling * Verify idempotency of hooks * Tricky to _verify_, and not an enforced convention at the moment, so not sure * be able to specify multiple scenarios * For functional tests, they are in fact exercising multiple charms. Should those sit within the charms, or outside since it's in fact exercising the whole graph? * The place for these composed tests seem to be the stack * As much data as possible should be collected about the running tests so that a broken charm can be debugged and fixed. * Provide rich artifacts for failure analysis * Ideally tests will be run in lock step mode, so that breaking charms can be individually identified, but this is hard because changes may be co-dependent * It would be nice to have interface-specific tests that can run against any charms that implement such interfaces. In addition to working as tests, this is also a pragmatic way to document the interface. * support gerrit-like topics? (What's that? :-) i.e., change-sets (across different branches) * We need a way to know which charms trigger which tests * Keep it simple * James mentioned he'd like to have that done by Alpha 1 (December) so that he can take that into account for the OpenStack testing effort. ACTIONS: [niemeyer] spec [james-page] add openstack tests Proposal below is too complicated, rejected (Kept for posterity) Proposal: Each charm has a tests directory Under tests, you have executables: __install__ -- test to run after charm is installed with no relations Then two directories: provides/ requires/ These directories have a directory underneath for each interface provided/required. Those directories contain executables to run. The test runner follows the following method: deploy charm wait for installed status run __install__ script, FAIL if exits non-zero destroy service for interface in provides ; do calculate graph of all charms in store which require interface and all of its dependency combinations deploy requiring charm w/ dependencies and providing service add-relation between requiring/providing for test in provides/interface ; do run test with name of deployed requiring service for interface in requires ; do repeat process above with provides/requires transposed Each commit to any branch in charm store will queue up a run with only that change applied, none that have been done after it, and record pass/fail -- Juju: automated testing of charms https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-charm-testing -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at:
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Come on, a fix can't be done for this 4 years on? In fact, between dbus and network-manager now waiting for the 'deconfiguring-networking' event before shutting down, and NM registering its child processes with /run/sendsigs.omit.d to fix bug #869635, I believe this should resolve the problem for the NM case in 12.04. Please test with the 12.04 beta and see if this isn't resolved for you. With all the various workarounds people have put in above comments, surely one of them can work for everyone?! Nope. All of those workarounds are specific to one configuration or another. ** Changed in: network-manager (Ubuntu) Status: Confirmed = Fix Released -- 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/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/211631/+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 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
wpasupplicant no longer includes an init script at all, so this task can also be considered fixed. ** Changed in: wpasupplicant (Ubuntu) Status: Confirmed = Fix Released -- 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/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/211631/+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 967296] [NEW] package libapache2-mod-php5 5.3.5-1ubuntu7.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Public bug reported: Automated error message popped up on first startup after Ubuntu distro upgrade using 'sudo apt-get dist-upgrade'. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: libapache2-mod-php5 5.3.5-1ubuntu7.7 ProcVersionSignature: Ubuntu 2.6.38-13.57-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 Architecture: i386 Date: Wed Mar 28 17:12:53 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) SourcePackage: php5 Title: package libapache2-mod-php5 5.3.5-1ubuntu7.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: Upgraded to natty on 2011-12-29 (90 days ago) ** Affects: php5 (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 php5 in Ubuntu. https://bugs.launchpad.net/bugs/967296 Title: package libapache2-mod-php5 5.3.5-1ubuntu7.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/967296/+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 967296] Re: package libapache2-mod-php5 5.3.5-1ubuntu7.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/967296 Title: package libapache2-mod-php5 5.3.5-1ubuntu7.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/967296/+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 967311] Re: Incorrect 6to4 handling
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/967311 Title: Incorrect 6to4 handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/967311/+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 967311] [NEW] Incorrect 6to4 handling
Public bug reported: If I run whois 2002:5634::, it tells me: Querying for the IPv4 endpoint 0.0.0.0 of a 6to4 IPv6 address. However that is not the correct endpoint for the address 2002:5634:: If OTOH I run 2002:5634:0::, it tells me: Querying for the IPv4 endpoint 86.52.0.0 of a 6to4 IPv6 address. Since 2002:5634:: and 2002:5634:0:: are different notations for the same IPv6 address, you'd expect whois to handle both the same, and extract the IPv4 address 86.52.0.0. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: whois 5.0.0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 Uname: Linux 2.6.32-37-generic i686 Architecture: i386 Date: Wed Mar 28 19:02:46 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) ProcEnviron: PATH=(custom, user) LANG=en_DK.utf8 SHELL=/bin/bash SourcePackage: whois ** Affects: whois (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/967311 Title: Incorrect 6to4 handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/967311/+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-p-juju-charm-testing] Juju: automated testing of charms
Blueprint changed by Mark Mims: Whiteboard changed: Status: Spec nearing final approval. Merge proposals submitted against juju to implement some parts of the wrapper inside juju itself: http://pad.lv/939932 , http://pad.lv/939944 Work Items: [clint-fewbar] write spec for charm testing facility: DONE implement specified testing framework: INPROGRESS [mark-mims] deploy testing framework for use with local provider (all phase1 tests are done w/ local provider): DONE - deploy testing framework for use against ec2: TODO - deploy testing framework for use against canonistack: TODO + [mark-mims] deploy testing framework for use against ec2: INPROGRESS + [mark-mims] deploy testing framework for use against canonistack: INPROGRESS deploy testing framework for use against orchestra (managing VMs instead of machines): POSTPONED write charm tests for mysql: POSTPONED [clint-fewbar] write charm tests for haproxy: POSTPONED [clint-fewbar] write charm tests for wordpress: POSTPONED [mark-mims] write charm tests for hadoop: POSTPONED [james-page] add openstack tests: TODO [mark-mims] jenkins charm to spawn basic charm tests: DONE [mark-mims] basic charm tests... just test install hooks for now: DONE Session notes: Welcome to Ubuntu Developer Summit! #uds-p #track #topic put your session notes here Requirements of automated testing of charms: * LET'S KEEP IT SIMPLE! :-) * Detect breakage of a charm relating to an interface * Identification of individual change which breaks a given relationship * Maybe implement tests that mock a relation to ensure implementers are compliant * Test dependent charms when a provider charm changes * Run test NxN of providers and requirers so all permutations are sane (_very_ expensive, probably impossible) * Run testing against multiple environment providers (EC2/OpenStack/BareMetal) * Notify maintainers when the charm breaks, rather than waiting for polling * Verify idempotency of hooks * Tricky to _verify_, and not an enforced convention at the moment, so not sure * be able to specify multiple scenarios * For functional tests, they are in fact exercising multiple charms. Should those sit within the charms, or outside since it's in fact exercising the whole graph? * The place for these composed tests seem to be the stack * As much data as possible should be collected about the running tests so that a broken charm can be debugged and fixed. * Provide rich artifacts for failure analysis * Ideally tests will be run in lock step mode, so that breaking charms can be individually identified, but this is hard because changes may be co-dependent * It would be nice to have interface-specific tests that can run against any charms that implement such interfaces. In addition to working as tests, this is also a pragmatic way to document the interface. * support gerrit-like topics? (What's that? :-) i.e., change-sets (across different branches) * We need a way to know which charms trigger which tests * Keep it simple * James mentioned he'd like to have that done by Alpha 1 (December) so that he can take that into account for the OpenStack testing effort. ACTIONS: [niemeyer] spec [james-page] add openstack tests Proposal below is too complicated, rejected (Kept for posterity) Proposal: Each charm has a tests directory Under tests, you have executables: __install__ -- test to run after charm is installed with no relations Then two directories: provides/ requires/ These directories have a directory underneath for each interface provided/required. Those directories contain executables to run. The test runner follows the following method: deploy charm wait for installed status run __install__ script, FAIL if exits non-zero destroy service for interface in provides ; do calculate graph of all charms in store which require interface and all of its dependency combinations deploy requiring charm w/ dependencies and providing service add-relation between requiring/providing for test in provides/interface ; do run test with name of deployed requiring service for interface in requires ; do repeat process above with provides/requires transposed Each commit to any branch in charm store will queue up a run with only that change applied, none that have been done after it, and record pass/fail -- Juju: automated testing of charms https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-charm-testing -- 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-p-juju-charm-testing] Juju: automated testing of charms
Blueprint changed by Mark Mims: Whiteboard changed: Status: Spec nearing final approval. Merge proposals submitted against juju to implement some parts of the wrapper inside juju itself: http://pad.lv/939932 , http://pad.lv/939944 Work Items: [clint-fewbar] write spec for charm testing facility: DONE implement specified testing framework: INPROGRESS - [mark-mims] deploy testing framework for use with local provider (all phase1 tests are done w/ local provider): DONE + [mark-mims] deploy testing framework for use with local provider (all phase1 tests and charm graph tests are done w/ local provider): DONE [mark-mims] deploy testing framework for use against ec2: INPROGRESS [mark-mims] deploy testing framework for use against canonistack: INPROGRESS deploy testing framework for use against orchestra (managing VMs instead of machines): POSTPONED write charm tests for mysql: POSTPONED [clint-fewbar] write charm tests for haproxy: POSTPONED [clint-fewbar] write charm tests for wordpress: POSTPONED [mark-mims] write charm tests for hadoop: POSTPONED [james-page] add openstack tests: TODO [mark-mims] jenkins charm to spawn basic charm tests: DONE [mark-mims] basic charm tests... just test install hooks for now: DONE Session notes: Welcome to Ubuntu Developer Summit! #uds-p #track #topic put your session notes here Requirements of automated testing of charms: * LET'S KEEP IT SIMPLE! :-) * Detect breakage of a charm relating to an interface * Identification of individual change which breaks a given relationship * Maybe implement tests that mock a relation to ensure implementers are compliant * Test dependent charms when a provider charm changes * Run test NxN of providers and requirers so all permutations are sane (_very_ expensive, probably impossible) * Run testing against multiple environment providers (EC2/OpenStack/BareMetal) * Notify maintainers when the charm breaks, rather than waiting for polling * Verify idempotency of hooks * Tricky to _verify_, and not an enforced convention at the moment, so not sure * be able to specify multiple scenarios * For functional tests, they are in fact exercising multiple charms. Should those sit within the charms, or outside since it's in fact exercising the whole graph? * The place for these composed tests seem to be the stack * As much data as possible should be collected about the running tests so that a broken charm can be debugged and fixed. * Provide rich artifacts for failure analysis * Ideally tests will be run in lock step mode, so that breaking charms can be individually identified, but this is hard because changes may be co-dependent * It would be nice to have interface-specific tests that can run against any charms that implement such interfaces. In addition to working as tests, this is also a pragmatic way to document the interface. * support gerrit-like topics? (What's that? :-) i.e., change-sets (across different branches) * We need a way to know which charms trigger which tests * Keep it simple * James mentioned he'd like to have that done by Alpha 1 (December) so that he can take that into account for the OpenStack testing effort. ACTIONS: [niemeyer] spec [james-page] add openstack tests Proposal below is too complicated, rejected (Kept for posterity) Proposal: Each charm has a tests directory Under tests, you have executables: __install__ -- test to run after charm is installed with no relations Then two directories: provides/ requires/ These directories have a directory underneath for each interface provided/required. Those directories contain executables to run. The test runner follows the following method: deploy charm wait for installed status run __install__ script, FAIL if exits non-zero destroy service for interface in provides ; do calculate graph of all charms in store which require interface and all of its dependency combinations deploy requiring charm w/ dependencies and providing service add-relation between requiring/providing for test in provides/interface ; do run test with name of deployed requiring service for interface in requires ; do repeat process above with provides/requires transposed Each commit to any branch in charm store will queue up a run with only that change applied, none that have been done after it, and record pass/fail -- Juju: automated testing of charms https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-charm-testing -- 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-p-juju-charm-testing] Juju: automated testing of charms
Blueprint changed by Mark Mims: Whiteboard changed: Status: Spec nearing final approval. Merge proposals submitted against juju to implement some parts of the wrapper inside juju itself: http://pad.lv/939932 , http://pad.lv/939944 Work Items: [clint-fewbar] write spec for charm testing facility: DONE - implement specified testing framework: INPROGRESS + implement specified testing framework (phase1): DONE [mark-mims] deploy testing framework for use with local provider (all phase1 tests and charm graph tests are done w/ local provider): DONE [mark-mims] deploy testing framework for use against ec2: INPROGRESS [mark-mims] deploy testing framework for use against canonistack: INPROGRESS deploy testing framework for use against orchestra (managing VMs instead of machines): POSTPONED write charm tests for mysql: POSTPONED [clint-fewbar] write charm tests for haproxy: POSTPONED [clint-fewbar] write charm tests for wordpress: POSTPONED [mark-mims] write charm tests for hadoop: POSTPONED [james-page] add openstack tests: TODO [mark-mims] jenkins charm to spawn basic charm tests: DONE [mark-mims] basic charm tests... just test install hooks for now: DONE Session notes: Welcome to Ubuntu Developer Summit! #uds-p #track #topic put your session notes here Requirements of automated testing of charms: * LET'S KEEP IT SIMPLE! :-) * Detect breakage of a charm relating to an interface * Identification of individual change which breaks a given relationship * Maybe implement tests that mock a relation to ensure implementers are compliant * Test dependent charms when a provider charm changes * Run test NxN of providers and requirers so all permutations are sane (_very_ expensive, probably impossible) * Run testing against multiple environment providers (EC2/OpenStack/BareMetal) * Notify maintainers when the charm breaks, rather than waiting for polling * Verify idempotency of hooks * Tricky to _verify_, and not an enforced convention at the moment, so not sure * be able to specify multiple scenarios * For functional tests, they are in fact exercising multiple charms. Should those sit within the charms, or outside since it's in fact exercising the whole graph? * The place for these composed tests seem to be the stack * As much data as possible should be collected about the running tests so that a broken charm can be debugged and fixed. * Provide rich artifacts for failure analysis * Ideally tests will be run in lock step mode, so that breaking charms can be individually identified, but this is hard because changes may be co-dependent * It would be nice to have interface-specific tests that can run against any charms that implement such interfaces. In addition to working as tests, this is also a pragmatic way to document the interface. * support gerrit-like topics? (What's that? :-) i.e., change-sets (across different branches) * We need a way to know which charms trigger which tests * Keep it simple * James mentioned he'd like to have that done by Alpha 1 (December) so that he can take that into account for the OpenStack testing effort. ACTIONS: [niemeyer] spec [james-page] add openstack tests Proposal below is too complicated, rejected (Kept for posterity) Proposal: Each charm has a tests directory Under tests, you have executables: __install__ -- test to run after charm is installed with no relations Then two directories: provides/ requires/ These directories have a directory underneath for each interface provided/required. Those directories contain executables to run. The test runner follows the following method: deploy charm wait for installed status run __install__ script, FAIL if exits non-zero destroy service for interface in provides ; do calculate graph of all charms in store which require interface and all of its dependency combinations deploy requiring charm w/ dependencies and providing service add-relation between requiring/providing for test in provides/interface ; do run test with name of deployed requiring service for interface in requires ; do repeat process above with provides/requires transposed Each commit to any branch in charm store will queue up a run with only that change applied, none that have been done after it, and record pass/fail -- Juju: automated testing of charms https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-charm-testing -- 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-p-juju-charm-testing] Juju: automated testing of charms
Blueprint changed by Mark Mims: Whiteboard changed: Status: Spec nearing final approval. Merge proposals submitted against juju to implement some parts of the wrapper inside juju itself: http://pad.lv/939932 , http://pad.lv/939944 Work Items: [clint-fewbar] write spec for charm testing facility: DONE implement specified testing framework (phase1): DONE [mark-mims] deploy testing framework for use with local provider (all phase1 tests and charm graph tests are done w/ local provider): DONE - [mark-mims] deploy testing framework for use against ec2: INPROGRESS - [mark-mims] deploy testing framework for use against canonistack: INPROGRESS + [mark-mims] deploy testing framework for use against ec2: POSTPONED (this is an out-of-cycle activity) + [mark-mims] deploy testing framework for use against canonistack: POSTPONED (this is an out-of-cycle activitly) deploy testing framework for use against orchestra (managing VMs instead of machines): POSTPONED write charm tests for mysql: POSTPONED [clint-fewbar] write charm tests for haproxy: POSTPONED [clint-fewbar] write charm tests for wordpress: POSTPONED [mark-mims] write charm tests for hadoop: POSTPONED [james-page] add openstack tests: TODO [mark-mims] jenkins charm to spawn basic charm tests: DONE [mark-mims] basic charm tests... just test install hooks for now: DONE Session notes: Welcome to Ubuntu Developer Summit! #uds-p #track #topic put your session notes here Requirements of automated testing of charms: * LET'S KEEP IT SIMPLE! :-) * Detect breakage of a charm relating to an interface * Identification of individual change which breaks a given relationship * Maybe implement tests that mock a relation to ensure implementers are compliant * Test dependent charms when a provider charm changes * Run test NxN of providers and requirers so all permutations are sane (_very_ expensive, probably impossible) * Run testing against multiple environment providers (EC2/OpenStack/BareMetal) * Notify maintainers when the charm breaks, rather than waiting for polling * Verify idempotency of hooks * Tricky to _verify_, and not an enforced convention at the moment, so not sure * be able to specify multiple scenarios * For functional tests, they are in fact exercising multiple charms. Should those sit within the charms, or outside since it's in fact exercising the whole graph? * The place for these composed tests seem to be the stack * As much data as possible should be collected about the running tests so that a broken charm can be debugged and fixed. * Provide rich artifacts for failure analysis * Ideally tests will be run in lock step mode, so that breaking charms can be individually identified, but this is hard because changes may be co-dependent * It would be nice to have interface-specific tests that can run against any charms that implement such interfaces. In addition to working as tests, this is also a pragmatic way to document the interface. * support gerrit-like topics? (What's that? :-) i.e., change-sets (across different branches) * We need a way to know which charms trigger which tests * Keep it simple * James mentioned he'd like to have that done by Alpha 1 (December) so that he can take that into account for the OpenStack testing effort. ACTIONS: [niemeyer] spec [james-page] add openstack tests Proposal below is too complicated, rejected (Kept for posterity) Proposal: Each charm has a tests directory Under tests, you have executables: __install__ -- test to run after charm is installed with no relations Then two directories: provides/ requires/ These directories have a directory underneath for each interface provided/required. Those directories contain executables to run. The test runner follows the following method: deploy charm wait for installed status run __install__ script, FAIL if exits non-zero destroy service for interface in provides ; do calculate graph of all charms in store which require interface and all of its dependency combinations deploy requiring charm w/ dependencies and providing service add-relation between requiring/providing for test in provides/interface ; do run test with name of deployed requiring service for interface in requires ; do repeat process above with provides/requires transposed Each commit to any branch in charm store will queue up a run with only that change applied, none that have been done after it, and record pass/fail -- Juju: automated testing of charms https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-charm-testing -- 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 925024] Re: apparmor makes it impossible to install postgresql-common on Precise
Hi James, can you confirm that if you /etc/init.d/apparmor stop /etc/init.d/apparmor teardown it then proceeds? Interesting that it's always dpkg-divert. I wonder what it does under the covers to trigger this? ** Changed in: linux (Ubuntu) Status: Fix Released = Confirmed ** Changed in: lxc (Ubuntu) Status: Invalid = Confirmed ** Changed in: linux (Ubuntu) Importance: Medium = 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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 967410] [NEW] Windows clients cannot connect to shared printers
Public bug reported: Since installing 12.04 I can no longer connect my windows XP clients to my laser printers on the Ubuntu system using samba. It works on 11.10 using the exact same smb.conf file. I can see the printers from the windows clients, I can select it, I install the drivers locally from the windows pc. When I click next I get the message Windows cannot connect to the printer. Either the printer name was typed incorrectly or the specified printer has lost its connection to the sever. This is a deal breaker for me. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 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/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967410/+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 924337] Re: lxc on precise is not working with lucid containers (container does not reach runlevel 2)
Confirmed - in fact /etc/init/lxcguest.conf is missing altogether, causing other problems as well. I'll push a fix to natty-proposed. Thanks for pointing this out. -- 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/924337 Title: lxc on precise is not working with lucid containers (container does not reach runlevel 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+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 118328] Invitation to connect on LinkedIn
LinkedIn Bug, I'd like to add you to my professional network on LinkedIn. - Michael Michael Cohne Associate Professor at Boston University Greater Boston Area Confirm that you know Michael Cohne: https://www.linkedin.com/e/-be33i9-h0cqimqz-2d/isd/6471152703/VN5MvrwM/?hs=falsetok=0XAd51ZaVf_l81 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-be33i9-h0cqimqz-2d/TkZJszXQCwbgWh9nYQmeQDrQPOQc5JPhW8ezF_j/goo/118328%40bugs%2Elaunchpad%2Enet/20061/I2245332742_1/?hs=falsetok=122bqweUVf_l81 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -- 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/118328 Title: Feisty smbmount fails with Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/118328/+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 118328] Invitation to connect on LinkedIn
LinkedIn Bug, I'd like to add you to my professional network on LinkedIn. - Michael Michael Cohne Associate Professor at Boston University Greater Boston Area Confirm that you know Michael Cohne: https://www.linkedin.com/e/-be33i9-h0cqlnsu-24/isd/6471152703/VN5MvrwM/?hs=falsetok=0hwQgjofxh_l81 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-be33i9-h0cqlnsu-24/TkZJszXQCwbgWh9nYQmeQDrQPOQc5JPhW8ezF_j/goo/118328%40bugs%2Elaunchpad%2Enet/20061/I2245339968_1/?hs=falsetok=0rgmzSYflh_l81 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -- 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/118328 Title: Feisty smbmount fails with Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/118328/+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 967311] Re: Incorrect 6to4 handling
** Changed in: whois (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/967311 Title: Incorrect 6to4 handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/967311/+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 966069] Re: /etc/apache2/conf.d/dashboard.conf contains wrong paths in the Ubuntu package
This bug is already targeted to the correct Ubuntu package, and the code in question is maintained by the other project entirely. Closing for this Horizon. ** Changed in: horizon Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/966069 Title: /etc/apache2/conf.d/dashboard.conf contains wrong paths in the Ubuntu package To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/966069/+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 967424] [NEW] Cobbler package silently creates invalid install if /var/www/cobbler directory already exists
Public bug reported: Using version cobbler-2.2.2-0ubuntu21 The install script attempts to create a link from /var/www/cobbler to /usr/share/cobbler/webroot/cobbler. My system had a previous manual installation of cobbler with a /var/www/cobbler directory (not a link). The installer does not create the link but did not report that the link could not be created. The web UI did not work properly until I moved the directory and reinstalled the package. Perhaps the install should fail if /var/www/cobbler link cannot be created? ** Affects: cobbler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/967424 Title: Cobbler package silently creates invalid install if /var/www/cobbler directory already exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/967424/+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 967430] [NEW] Switching to internal python tftp server fails due to file name change
Public bug reported: Using cobbler-2.2.2-0ubuntu21 The cobbler project ships an internal python tftpd.py server. If modules.conf is changed to use this, then the /etc/cobbler/tftpd.template file is used to create an xinitd service entry. This template contains an entry called binary which then substitutes the binary name /usr/sbin/tftpd.py The ubuntu packaging has renamed tftpd.py to tftpd but the template substitution incorrectly uses /usr/sbin/tftpd.py. The workaround is simple: Hard code the template file to use /usr/sbin/tftpd. ** Affects: cobbler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/967430 Title: Switching to internal python tftp server fails due to file name change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/967430/+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 781949] Re: Must check certificates for validity
** Changed in: juju Milestone: None = florence -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to txaws in Ubuntu. https://bugs.launchpad.net/bugs/781949 Title: Must check certificates for validity To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/781949/+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-p-juju-charm-testing] Juju: automated testing of charms
Blueprint changed by Chris Johnston: Whiteboard changed: Status: Spec nearing final approval. Merge proposals submitted against juju to implement some parts of the wrapper inside juju itself: http://pad.lv/939932 , http://pad.lv/939944 Work Items: [clint-fewbar] write spec for charm testing facility: DONE implement specified testing framework (phase1): DONE [mark-mims] deploy testing framework for use with local provider (all phase1 tests and charm graph tests are done w/ local provider): DONE - [mark-mims] deploy testing framework for use against ec2: POSTPONED (this is an out-of-cycle activity) - [mark-mims] deploy testing framework for use against canonistack: POSTPONED (this is an out-of-cycle activitly) + [mark-mims] deploy testing framework for use against ec2 (this is an out-of-cycle activity): POSTPONED + [mark-mims] deploy testing framework for use against canonistack (this is an out-of-cycle activitly): POSTPONED deploy testing framework for use against orchestra (managing VMs instead of machines): POSTPONED write charm tests for mysql: POSTPONED [clint-fewbar] write charm tests for haproxy: POSTPONED [clint-fewbar] write charm tests for wordpress: POSTPONED [mark-mims] write charm tests for hadoop: POSTPONED [james-page] add openstack tests: TODO [mark-mims] jenkins charm to spawn basic charm tests: DONE [mark-mims] basic charm tests... just test install hooks for now: DONE Session notes: Welcome to Ubuntu Developer Summit! #uds-p #track #topic put your session notes here Requirements of automated testing of charms: * LET'S KEEP IT SIMPLE! :-) * Detect breakage of a charm relating to an interface * Identification of individual change which breaks a given relationship * Maybe implement tests that mock a relation to ensure implementers are compliant * Test dependent charms when a provider charm changes * Run test NxN of providers and requirers so all permutations are sane (_very_ expensive, probably impossible) * Run testing against multiple environment providers (EC2/OpenStack/BareMetal) * Notify maintainers when the charm breaks, rather than waiting for polling * Verify idempotency of hooks * Tricky to _verify_, and not an enforced convention at the moment, so not sure * be able to specify multiple scenarios * For functional tests, they are in fact exercising multiple charms. Should those sit within the charms, or outside since it's in fact exercising the whole graph? * The place for these composed tests seem to be the stack * As much data as possible should be collected about the running tests so that a broken charm can be debugged and fixed. * Provide rich artifacts for failure analysis * Ideally tests will be run in lock step mode, so that breaking charms can be individually identified, but this is hard because changes may be co-dependent * It would be nice to have interface-specific tests that can run against any charms that implement such interfaces. In addition to working as tests, this is also a pragmatic way to document the interface. * support gerrit-like topics? (What's that? :-) i.e., change-sets (across different branches) * We need a way to know which charms trigger which tests * Keep it simple * James mentioned he'd like to have that done by Alpha 1 (December) so that he can take that into account for the OpenStack testing effort. ACTIONS: [niemeyer] spec [james-page] add openstack tests Proposal below is too complicated, rejected (Kept for posterity) Proposal: Each charm has a tests directory Under tests, you have executables: __install__ -- test to run after charm is installed with no relations Then two directories: provides/ requires/ These directories have a directory underneath for each interface provided/required. Those directories contain executables to run. The test runner follows the following method: deploy charm wait for installed status run __install__ script, FAIL if exits non-zero destroy service for interface in provides ; do calculate graph of all charms in store which require interface and all of its dependency combinations deploy requiring charm w/ dependencies and providing service add-relation between requiring/providing for test in provides/interface ; do run test with name of deployed requiring service for interface in requires ; do repeat process above with provides/requires transposed Each commit to any branch in charm store will queue up a run with only that change applied, none that have been done after it, and record pass/fail -- Juju: automated testing of charms https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-charm-testing -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at:
[Bug 542543] Re: Access denied for user 'root'@'localhost' to database SOMEDB
Clint, is there a way to fix this for those of us in this unpleasant situation? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/542543 Title: Access denied for user 'root'@'localhost' to database SOMEDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/542543/+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-p-juju-charm-testing] Juju: automated testing of charms
Blueprint changed by James Page: Whiteboard changed: Status: Spec nearing final approval. Merge proposals submitted against juju to implement some parts of the wrapper inside juju itself: http://pad.lv/939932 , http://pad.lv/939944 Work Items: [clint-fewbar] write spec for charm testing facility: DONE implement specified testing framework (phase1): DONE [mark-mims] deploy testing framework for use with local provider (all phase1 tests and charm graph tests are done w/ local provider): DONE [mark-mims] deploy testing framework for use against ec2 (this is an out-of-cycle activity): POSTPONED [mark-mims] deploy testing framework for use against canonistack (this is an out-of-cycle activitly): POSTPONED deploy testing framework for use against orchestra (managing VMs instead of machines): POSTPONED write charm tests for mysql: POSTPONED [clint-fewbar] write charm tests for haproxy: POSTPONED [clint-fewbar] write charm tests for wordpress: POSTPONED [mark-mims] write charm tests for hadoop: POSTPONED - [james-page] add openstack tests: TODO + [james-page] add openstack tests: DONE [mark-mims] jenkins charm to spawn basic charm tests: DONE [mark-mims] basic charm tests... just test install hooks for now: DONE Session notes: Welcome to Ubuntu Developer Summit! #uds-p #track #topic put your session notes here Requirements of automated testing of charms: * LET'S KEEP IT SIMPLE! :-) * Detect breakage of a charm relating to an interface * Identification of individual change which breaks a given relationship * Maybe implement tests that mock a relation to ensure implementers are compliant * Test dependent charms when a provider charm changes * Run test NxN of providers and requirers so all permutations are sane (_very_ expensive, probably impossible) * Run testing against multiple environment providers (EC2/OpenStack/BareMetal) * Notify maintainers when the charm breaks, rather than waiting for polling * Verify idempotency of hooks * Tricky to _verify_, and not an enforced convention at the moment, so not sure * be able to specify multiple scenarios * For functional tests, they are in fact exercising multiple charms. Should those sit within the charms, or outside since it's in fact exercising the whole graph? * The place for these composed tests seem to be the stack * As much data as possible should be collected about the running tests so that a broken charm can be debugged and fixed. * Provide rich artifacts for failure analysis * Ideally tests will be run in lock step mode, so that breaking charms can be individually identified, but this is hard because changes may be co-dependent * It would be nice to have interface-specific tests that can run against any charms that implement such interfaces. In addition to working as tests, this is also a pragmatic way to document the interface. * support gerrit-like topics? (What's that? :-) i.e., change-sets (across different branches) * We need a way to know which charms trigger which tests * Keep it simple * James mentioned he'd like to have that done by Alpha 1 (December) so that he can take that into account for the OpenStack testing effort. ACTIONS: [niemeyer] spec [james-page] add openstack tests Proposal below is too complicated, rejected (Kept for posterity) Proposal: Each charm has a tests directory Under tests, you have executables: __install__ -- test to run after charm is installed with no relations Then two directories: provides/ requires/ These directories have a directory underneath for each interface provided/required. Those directories contain executables to run. The test runner follows the following method: deploy charm wait for installed status run __install__ script, FAIL if exits non-zero destroy service for interface in provides ; do calculate graph of all charms in store which require interface and all of its dependency combinations deploy requiring charm w/ dependencies and providing service add-relation between requiring/providing for test in provides/interface ; do run test with name of deployed requiring service for interface in requires ; do repeat process above with provides/requires transposed Each commit to any branch in charm store will queue up a run with only that change applied, none that have been done after it, and record pass/fail -- Juju: automated testing of charms https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-charm-testing -- 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-p-juju-charm-testing] Juju: automated testing of charms
Blueprint changed by Clint Byrum: Whiteboard changed: Status: Spec nearing final approval. Merge proposals submitted against juju to implement some parts of the wrapper inside juju itself: http://pad.lv/939932 , http://pad.lv/939944 Work Items: [clint-fewbar] write spec for charm testing facility: DONE - implement specified testing framework (phase1): DONE + [mark-mims] implement specified testing framework (phase1): DONE + implement specified testing framework (phase2) ( blocked on merge of http://pad.lv/939944 ): BLOCKED [mark-mims] deploy testing framework for use with local provider (all phase1 tests and charm graph tests are done w/ local provider): DONE [mark-mims] deploy testing framework for use against ec2 (this is an out-of-cycle activity): POSTPONED [mark-mims] deploy testing framework for use against canonistack (this is an out-of-cycle activitly): POSTPONED deploy testing framework for use against orchestra (managing VMs instead of machines): POSTPONED write charm tests for mysql: POSTPONED [clint-fewbar] write charm tests for haproxy: POSTPONED [clint-fewbar] write charm tests for wordpress: POSTPONED [mark-mims] write charm tests for hadoop: POSTPONED [james-page] add openstack tests: DONE [mark-mims] jenkins charm to spawn basic charm tests: DONE [mark-mims] basic charm tests... just test install hooks for now: DONE Session notes: Welcome to Ubuntu Developer Summit! #uds-p #track #topic put your session notes here Requirements of automated testing of charms: * LET'S KEEP IT SIMPLE! :-) * Detect breakage of a charm relating to an interface * Identification of individual change which breaks a given relationship * Maybe implement tests that mock a relation to ensure implementers are compliant * Test dependent charms when a provider charm changes * Run test NxN of providers and requirers so all permutations are sane (_very_ expensive, probably impossible) * Run testing against multiple environment providers (EC2/OpenStack/BareMetal) * Notify maintainers when the charm breaks, rather than waiting for polling * Verify idempotency of hooks * Tricky to _verify_, and not an enforced convention at the moment, so not sure * be able to specify multiple scenarios * For functional tests, they are in fact exercising multiple charms. Should those sit within the charms, or outside since it's in fact exercising the whole graph? * The place for these composed tests seem to be the stack * As much data as possible should be collected about the running tests so that a broken charm can be debugged and fixed. * Provide rich artifacts for failure analysis * Ideally tests will be run in lock step mode, so that breaking charms can be individually identified, but this is hard because changes may be co-dependent * It would be nice to have interface-specific tests that can run against any charms that implement such interfaces. In addition to working as tests, this is also a pragmatic way to document the interface. * support gerrit-like topics? (What's that? :-) i.e., change-sets (across different branches) * We need a way to know which charms trigger which tests * Keep it simple * James mentioned he'd like to have that done by Alpha 1 (December) so that he can take that into account for the OpenStack testing effort. ACTIONS: [niemeyer] spec [james-page] add openstack tests Proposal below is too complicated, rejected (Kept for posterity) Proposal: Each charm has a tests directory Under tests, you have executables: __install__ -- test to run after charm is installed with no relations Then two directories: provides/ requires/ These directories have a directory underneath for each interface provided/required. Those directories contain executables to run. The test runner follows the following method: deploy charm wait for installed status run __install__ script, FAIL if exits non-zero destroy service for interface in provides ; do calculate graph of all charms in store which require interface and all of its dependency combinations deploy requiring charm w/ dependencies and providing service add-relation between requiring/providing for test in provides/interface ; do run test with name of deployed requiring service for interface in requires ; do repeat process above with provides/requires transposed Each commit to any branch in charm store will queue up a run with only that change applied, none that have been done after it, and record pass/fail -- Juju: automated testing of charms https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-charm-testing -- 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 959426] Re: nova + glance services die if started before db is reachable
Reviewed: https://review.openstack.org/5911 Committed: http://github.com/openstack/glance/commit/127101a44c0708ef26572abf98a025983ae35aa4 Submitter: Jenkins Branch:milestone-proposed commit 127101a44c0708ef26572abf98a025983ae35aa4 Author: Adam Gandelman ad...@canonical.com Date: Fri Mar 23 18:23:54 2012 -0700 Ensure functional db connection in configure_db() During initial database setup, ensure we can physically connect to the database and allow a failed connection to make use of the new retry mechanism instead of registry startup failing outright. Fixes lp bug #959426. Change-Id: I1c87b19913c4204465e5d2027f2f184f0f358fd0 ** Changed in: glance Status: Fix Committed = Fix Released -- 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/959426 Title: nova + glance services die if started before db is reachable To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/959426/+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 542543] Re: Access denied for user 'root'@'localhost' to database SOMEDB
I got it fixed, thanks to post #4 on this thread: http://ubuntuforums.org/showthread.php?t=1836919 Start your mysql client as shown below: mysql -u debian-sys-maint -p In another terminal, 'cat' the file /etc/mysql/debian.cnf (you'll have to 'sudo cat' it). That file contains a password; paste that password in the first terminal when prompted for it. Then execute the following commands at the 'mysql' prompt: grant all privileges on *.* to 'root'@'localhost' identified by 't1g3r' with grant option; flush privileges; That did it for me! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/542543 Title: Access denied for user 'root'@'localhost' to database SOMEDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/542543/+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 967815] [NEW] /var/lib/tftpboot directory permissions destroyed
Public bug reported:
Every so often -- in fact whenever a new debian-installer is released
for Precise -- we re-import the distro. In the process, the TFTP boot
files are regenerated.
Somehow this changes /var/lib/tftpboot permissions on subdirectories and
files. The result is NOT guaranteed to be bad, and it is NOT guaranteed
to affect the same directories and files in the same way.
For example, the last occurence (today) shows only this change:
55,56c55,56
drwxr-xr-x 2 root root 4096 2012-03-22 23:13 precise-i386
drwxr-xr-x 2 root root 4096 2012-03-22 23:13 precise-x86_64
---
d-w---x--- 2 root root 4096 2012-03-28 04:31 precise-i386
d-w---x--- 2 root root 4096 2012-03-28 04:31 precise-x86_64
Notice the completely hosed permissions on the new directories.
As a result PXE booting may fail (in this case DID fail).
This is a serious issue, impacting automated testing.
WORKAROUND:
find /var/lib/tftpboot -type d -exec sudo chmod 755 {} \;
find /var/lib/tftpboot -type f -exec sudo chmod 644 {} \;
but this is rather ridiculous ;-)
ProblemType: BugDistroRelease: Ubuntu 11.10
Package: cobbler 2.1.0+git20110602-0ubuntu26.2
ProcVersionSignature: Ubuntu 3.0.0-12.20-server 3.0.4
Uname: Linux 3.0.0-12-server x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Mar 28 21:52:56 2012InstallationMedia: Ubuntu-Server 11.04 Natty
Narwhal - Release amd64 (20110426)
PackageArchitecture: allSourcePackage: cobblerUpgradeStatus: Upgraded to
oneiric on 2011-11-16 (133 days ago)
** Affects: cobbler (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug oneiric qa-manual-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/967815
Title:
/var/lib/tftpboot directory permissions destroyed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/967815/+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 967815] Re: /var/lib/tftpboot directory permissions destroyed
** Attachment added: directory /var/lib/tftpboot before re-importing a distro https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/967815/+attachment/2957200/+files/tftpboot.dir-before -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/967815 Title: /var/lib/tftpboot directory permissions destroyed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/967815/+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 967815] Re: /var/lib/tftpboot directory permissions destroyed
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/967815 Title: /var/lib/tftpboot directory permissions destroyed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/967815/+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 967815] Re: /var/lib/tftpboot directory permissions destroyed
** Attachment added: /var/lib/tftpboot after importing the distro
https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/967815/+attachment/2957201/+files/tftpboot.dir-after
** Description changed:
Every so often -- in fact whenever a new debian-installer is released
for Precise -- we re-import the distro. In the process, the TFTP boot
files are regenerated.
Somehow this changes /var/lib/tftpboot permissions on subdirectories and
files. The result is NOT guaranteed to be bad, and it is NOT guaranteed
to affect the same directories and files in the same way.
For example, the last occurence (today) shows only this change:
-
55,56c55,56
drwxr-xr-x 2 root root 4096 2012-03-22 23:13 precise-i386
drwxr-xr-x 2 root root 4096 2012-03-22 23:13 precise-x86_64
---
d-w---x--- 2 root root 4096 2012-03-28 04:31 precise-i386
d-w---x--- 2 root root 4096 2012-03-28 04:31 precise-x86_64
Notice the completely hosed permissions on the new directories.
As a result PXE booting may fail (in this case DID fail).
This is a serious issue, impacting automated testing.
- ProblemType: Bug
- DistroRelease: Ubuntu 11.10
+ WORKAROUND:
+
+ find /var/lib/tftpboot -type d -exec sudo chmod 755 {} \;
+ find /var/lib/tftpboot -type f -exec sudo chmod 644 {} \;
+
+ but this is rather ridiculous ;-)
+
+ ProblemType: BugDistroRelease: Ubuntu 11.10
Package: cobbler 2.1.0+git20110602-0ubuntu26.2
ProcVersionSignature: Ubuntu 3.0.0-12.20-server 3.0.4
Uname: Linux 3.0.0-12-server x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
- Date: Wed Mar 28 21:52:56 2012
- InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64
(20110426)
- PackageArchitecture: all
- SourcePackage: cobbler
- UpgradeStatus: Upgraded to oneiric on 2011-11-16 (133 days ago)
+ Date: Wed Mar 28 21:52:56 2012InstallationMedia: Ubuntu-Server 11.04 Natty
Narwhal - Release amd64 (20110426)
+ PackageArchitecture: allSourcePackage: cobblerUpgradeStatus: Upgraded to
oneiric on 2011-11-16 (133 days ago)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/967815
Title:
/var/lib/tftpboot directory permissions destroyed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/967815/+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 959352] Re: Ephemeral containers have /rootfs prefix in /proc/self/maps entries
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: needs-upstream-testing -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 569757] Re: NIS upstart dependency broken for lucid
A user has contacted me privately to report a regression with the package in -proposed: I think I updated the nis package yesterday through the ubuntu update process. This morning nis did not work anymore. The solution was that /etc/init/ypbind.conf is waiting for a local server which is obviously not running when you use another server. I commented out the lines 43-45 and now it's working. The issue here is a wrong check in the ypbind pre-start script. We're accidentally trying to start ypserv in all cases that we're running ypbind, when we should only be trying to start it if NISSERVER is set to a value other than false. Marked verification-failed; I'll work on preparing a new package. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+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 569757] Re: NIS upstart dependency broken for lucid
** Changed in: nis (Ubuntu Lucid) Status: Fix Committed = In Progress ** Changed in: nis (Ubuntu Oneiric) Status: Fix Committed = In Progress ** Changed in: nis (Ubuntu Natty) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+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 569757] Re: NIS upstart dependency broken for lucid
Is that what broke? I tried it Monday and my NIS broke and reverting didn't fix it. I never checked the configs though. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+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 959426] Re: nova + glance services die if started before db is reachable
Fix proposed to branch: master Review: https://review.openstack.org/5939 ** Changed in: nova Status: Triaged = In Progress -- 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/959426 Title: nova + glance services die if started before db is reachable To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/959426/+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 573318] Re: mysql server will not start
The problem for me was that the file /etc/apparmor.d/local/usr.sbin.mysqld did not exist after the upgrade. I manually copied one from one of the empty ones (i.e. only had header comment) and then everything was good to go. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/573318 Title: mysql server will not start To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/573318/+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 542543] Re: Access denied for user 'root'@'localhost' to database SOMEDB
I put a password in that last comment like a complete idiot. Well, I've changed it, and if you try to follow along you'll want to substitute 't1g3r' in the above grant command to whatever you want your root mysql password to be. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/542543 Title: Access denied for user 'root'@'localhost' to database SOMEDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/542543/+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 875950] Re: /var/run/dnsmasq/resolv.conf empty on boot
On further inspection, it did not solve the problem. restarting the networking along with the fix of the gateway solved the problem. To get it working reliably, I had to add: ifdown eth1 ifup eth1 into /etc/init.d/dnsmasq in the start section. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/875950 Title: /var/run/dnsmasq/resolv.conf empty on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/875950/+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
