Re: [Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
Quoting David Favor (da...@davidfavor.com): Correct. It appears the default template processing (default meaning no template specified) seems like it could use a bit of work. Ok, thanks. Seems like specifying no template should either throw an error or create some form of container that will start. For anyone reading this report who may not be clear on it, the current behavior is: a template exists to fill in a rootfs. If no template is specified, then it is assumed that a rootfs has already been created, and only the basic metadata (rootfs location etc) are to be filled in. People do rely on this behavior. So the question is how to best avoid the (more common imo) case where a user accidentally does not specify a template. We could force the existing no-template users to switch to specifying '-t none'. We could simply document the current behavior. We could print out a warning about there being no template, but not change the default behavior. Not sure if there are any other ideas. So the question is how to best handle this without causing trouble for people who rely on this default behavior. subject: change default template handling status: triaged importance: wishlist ** Changed in: libcgroup (Ubuntu) Importance: Undecided = Wishlist ** Changed in: libcgroup (Ubuntu) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1271000 Title: lxc-start fails with Out of memory reading cgroups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+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-s-server-app-banner-updates] Server Application Banner Updates
Blueprint changed by Yolanda Robla: Work items changed: Work items for ubuntu-14.04: [yolanda.robla] Check, enable, and test apache2: DONE [yolanda.robla] Check, enable, and test bind9: DONE [yolanda.robla] Check, enable, and test dovecot (imapd): DONE [yolanda.robla] Check, enable, and test dovecot (pop3d): DONE [yolanda.robla] Check, enable, and test exim4: DONE [yolanda.robla] Check, enable, and test mysql-server: DONE [yolanda.robla] Check, enable, and test postgresql: DONE [yolanda.robla] Check, enable, and test openldap: DONE [yolanda.robla] Check, enable, and test openssh: DONE - [yolanda.robla] Check, enable, and test openstack (proposal sent upstream, waiting for feeback): TODO + [yolanda.robla] Check, enable, and test openstack (keystone): DONE [yolanda.robla] Check, enable, and test postfix: DONE [yolanda.robla] Check, enable, and test squid3: DONE [yolanda.robla] Check, enable, and test tomcat7: DONE [yolanda.robla] Check, enable, and test nginx: DONE [yolanda.robla] Check, enable, and test python-django: DONE [yolanda.robla] Check, enable, and test memcached: DONE [yolanda.robla] Check, enable, and test couchdb: DONE [yolanda.robla] Check, enable, and test nodejs: DONE -- Server Application Banner Updates https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-server-app-banner-updates -- 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 1273447] Re: samba sharing doesn't work on fresh Ubuntu 14.04 x64 build - net usershare add: cannot convert name Everyone to a SID. Access denied
*** This bug is a duplicate of bug 1261873 *** https://bugs.launchpad.net/bugs/1261873 ** This bug has been marked a duplicate of bug 1261873 'net usershare' returned error 255 -- 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/1273447 Title: samba sharing doesn't work on fresh Ubuntu 14.04 x64 build - net usershare add: cannot convert name Everyone to a SID. Access denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1273447/+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 1210936] Re: Warnings in munin-graph.log during each graph rendering run
The recent update of Munin (Ubuntu Security Notice USN-2090-1, Munin 1.4.6-3ubuntu3.4) still has this issue, so the patch had to be applied manually (again). -- 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/1210936 Title: Warnings in munin-graph.log during each graph rendering run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1210936/+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 1180281] Re: “Unable to connect to libvirt” when using virt-manager with the xl toolstack and Xen 4.2.1
Has this been tested in 14.04 with libvirt 1.2.1? There was a bug when merging libvirt 1.2.0 which should be resolved now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1180281 Title: “Unable to connect to libvirt” when using virt-manager with the xl toolstack and Xen 4.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281/+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
Re: [Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough
If I understand correctly, the new libvirt version I just pushed should fix this bug. Please re-mark Confirmed if I am wrong and more patches are needed. status: fixreleased ** Changed in: libvirt (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu mode = host- passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1262641/+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 1271617] Re: [mir] python-taskflow
Override component to main python-taskflow 0.1.2-0ubuntu3 in trusty: universe/python - main python-taskflow 0.1.2-0ubuntu3 in trusty amd64: universe/python/optional/100% - main python-taskflow 0.1.2-0ubuntu3 in trusty arm64: universe/python/optional/100% - main python-taskflow 0.1.2-0ubuntu3 in trusty armhf: universe/python/optional/100% - main python-taskflow 0.1.2-0ubuntu3 in trusty i386: universe/python/optional/100% - main python-taskflow 0.1.2-0ubuntu3 in trusty powerpc: universe/python/optional/100% - main python-taskflow 0.1.2-0ubuntu3 in trusty ppc64el: universe/python/optional/100% - main 7 publications overridden. ** Changed in: python-taskflow (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-taskflow in Ubuntu. https://bugs.launchpad.net/bugs/1271617 Title: [mir] python-taskflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-taskflow/+bug/1271617/+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 1271609] Re: [MIR] python-networkx
Override component to main python-networkx 1.8.1-0ubuntu3 in trusty: universe/graphics - main python-networkx 1.8.1-0ubuntu3 in trusty amd64: universe/graphics/optional/100% - main python-networkx 1.8.1-0ubuntu3 in trusty arm64: universe/graphics/optional/100% - main python-networkx 1.8.1-0ubuntu3 in trusty armhf: universe/graphics/optional/100% - main python-networkx 1.8.1-0ubuntu3 in trusty i386: universe/graphics/optional/100% - main python-networkx 1.8.1-0ubuntu3 in trusty powerpc: universe/graphics/optional/100% - main python-networkx 1.8.1-0ubuntu3 in trusty ppc64el: universe/graphics/optional/100% - main python-networkx-doc 1.8.1-0ubuntu3 in trusty amd64: universe/doc/optional/100% - main python-networkx-doc 1.8.1-0ubuntu3 in trusty arm64: universe/doc/optional/100% - main python-networkx-doc 1.8.1-0ubuntu3 in trusty armhf: universe/doc/optional/100% - main python-networkx-doc 1.8.1-0ubuntu3 in trusty i386: universe/doc/optional/100% - main python-networkx-doc 1.8.1-0ubuntu3 in trusty powerpc: universe/doc/optional/100% - main python-networkx-doc 1.8.1-0ubuntu3 in trusty ppc64el: universe/doc/optional/100% - main python3-networkx 1.8.1-0ubuntu3 in trusty amd64: universe/python/optional/100% - main python3-networkx 1.8.1-0ubuntu3 in trusty arm64: universe/python/optional/100% - main python3-networkx 1.8.1-0ubuntu3 in trusty armhf: universe/python/optional/100% - main python3-networkx 1.8.1-0ubuntu3 in trusty i386: universe/python/optional/100% - main python3-networkx 1.8.1-0ubuntu3 in trusty powerpc: universe/python/optional/100% - main python3-networkx 1.8.1-0ubuntu3 in trusty ppc64el: universe/python/optional/100% - main 19 publications overridden. ** Changed in: python-networkx (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-networkx in Ubuntu. https://bugs.launchpad.net/bugs/1271609 Title: [MIR] python-networkx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-networkx/+bug/1271609/+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 1259985] Re: [MIR] oslo.rootwrap
Override component to main oslo.rootwrap 1.0.0-0ubuntu1 in trusty: universe/python - main python-oslo.rootwrap 1.0.0-0ubuntu1 in trusty amd64: universe/python/optional/100% - main python-oslo.rootwrap 1.0.0-0ubuntu1 in trusty arm64: universe/python/optional/100% - main python-oslo.rootwrap 1.0.0-0ubuntu1 in trusty armhf: universe/python/optional/100% - main python-oslo.rootwrap 1.0.0-0ubuntu1 in trusty i386: universe/python/optional/100% - main python-oslo.rootwrap 1.0.0-0ubuntu1 in trusty powerpc: universe/python/optional/100% - main python-oslo.rootwrap 1.0.0-0ubuntu1 in trusty ppc64el: universe/python/optional/100% - main 7 publications overridden. ** Changed in: oslo.rootwrap (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to oslo.rootwrap in Ubuntu. https://bugs.launchpad.net/bugs/1259985 Title: [MIR] oslo.rootwrap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oslo.rootwrap/+bug/1259985/+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 1271606] Re: [MIR] python-concurrent.futures
$ ./change-override -c main -S -y python-concurrent.futures Override component to main python-concurrent.futures 2.1.6-1ubuntu1 in trusty: universe/python - main python-concurrent.futures 2.1.6-1ubuntu1 in trusty amd64: universe/python/optional/100% - main python-concurrent.futures 2.1.6-1ubuntu1 in trusty arm64: universe/python/optional/100% - main python-concurrent.futures 2.1.6-1ubuntu1 in trusty armhf: universe/python/optional/100% - main python-concurrent.futures 2.1.6-1ubuntu1 in trusty i386: universe/python/optional/100% - main python-concurrent.futures 2.1.6-1ubuntu1 in trusty powerpc: universe/python/optional/100% - main python-concurrent.futures 2.1.6-1ubuntu1 in trusty ppc64el: universe/python/optional/100% - main 7 publications overridden. ** Changed in: python-concurrent.futures (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-concurrent.futures in Ubuntu. https://bugs.launchpad.net/bugs/1271606 Title: [MIR] python-concurrent.futures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-concurrent.futures/+bug/1271606/+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 1273654] [NEW] qemu-arm64-static binfmt registration for non-existent binary
Public bug reported: $ cat /proc/sys/fs/binfmt_misc/qemu-arm64 enabled interpreter /usr/bin/qemu-arm64-static flags: offset 0 magic 7f454c46020101000200b7 mask ff00fe $ ls -l /usr/bin/qemu-arm64-static ls: cannot access /usr/bin/qemu-arm64-static: No such file or directory $ Evidently this registration shouldn't be there. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-user-static 1.7.0+dfsg-2ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 28 12:06:47 2014 InstallationDate: Installed on 2010-09-24 (1222 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2013-10-23 (97 days ago) ** Affects: qemu (Ubuntu) Importance: High Assignee: Serge Hallyn (serge-hallyn) Status: Triaged ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1273654 Title: qemu-arm64-static binfmt registration for non-existent binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1273654/+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 1273654] Re: qemu-arm64-static binfmt registration for non-existent binary
** Changed in: qemu (Ubuntu) Status: New = Triaged ** Changed in: qemu (Ubuntu) Importance: Undecided = High ** Changed in: qemu (Ubuntu) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1273654 Title: qemu-arm64-static binfmt registration for non-existent binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1273654/+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 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build [error: implicit declaration of function ‘d_alloc_root’]
Just as a note, the new kernels are not only needed on LTS for hardware enablement (and I'm guessing relatively few people need hardware enablement in a VMware guest), but also to run Docker, which I suspect affects more people (me included). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build [error: implicit declaration of function ‘d_alloc_root’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+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 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
I didn't look too much into this, but would it be possible to make lxc- wait check the container's runlevel, and have a new booted state (unless you want to change the meaning of RUNNING) become true once the runlevel stops being unknown or N or S? -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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 1267393] Re: [MIR] juju-core, juju-mongodb
** Also affects: gccgo-go (Ubuntu) Importance: Undecided Status: New ** Changed in: gccgo-go (Ubuntu) Importance: Undecided = High ** Summary changed: - [MIR] juju-core, juju-mongodb + [MIR] juju-core, juju-mongodb, gccgo-go -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+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 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go
** Description changed: + gccgo-go + + Availability + + + In universe, available on all required architectures (x86, armhf, arm64, + ppc64el). + + Rationale + - + + 'go' build tool built using gccgo, avoiding the need to promote two + golang toolchains to Ubuntu main. + + Security + + + Searching for golang CVE's turned up nothing (this package is a rename + of the golang 1.2 source package). + + Quality assurance + - + + Package installs cleanly, go tool installed using alternatives at higher + priority that golang-go version in univers. + + Dependencies + + + gccgo is in universe, all other dependencies in main. + + Standards compliance + + + OK + + + Maintenance + --- + + Some bugs expected upfront but should stabilize before release. Probably + picked up by ubuntu-server if foundations team don't want to. + + Background information + -- + + This package is a re-cut of the golang upstream codebase with selected + cherry-picks from upstream VCS for gccgo support, along with a patch to + support building using gccgo + Make. + + The only code actually used is in src/cmd/go. + juju-mongodb Availability In universe, available on all required architectures (x86, armhf, arm64, ppc64el). Rationale - MongoDB is a dependency for operating a Juju deployed Ubuntu environment. Security MongoDB has had some CVE's in the past, related to the use of the V8 and Spidermonkey Javascript engine in the Mongo Shell; however juju-mongodb builds without support for Javascript scripting, avoiding the historic CVE's (which where fixed upstream anyway). Quality assurance - Package installs cleanly, package build process runs upstream smoke tests (minus jstests due to disabling javascript support). Tests pass on all architectures. Dependencies All in main already Standards compliance OK (well is scons but we won't hold that against it) Maintenance --- Upstream MongoDB run stable releases with point updates; its intended that a MRE is applied for this package so point releases can be pushed as SRU's. Its also possible that we might need to bump a major version (2.4.x - 2.6.x); as this package is specific to Juju, we can constrain the impact and regression testing to Juju only. Background information -- Why a separate package? it was agreed at the last vUDS that having a separate package allows us to limit a) use of v8 (disabled) which was a security concern and b) allows us to potentially update at a later date if need be only impacting juju itself. juju-core Availability In universe, not yet available on arm64 or ppc64el. Rationale - Juju is the recommended service orchestration tool for Ubuntu; as such it really needs to be a core part of Ubuntu. Security No security history, but it was agreed that a security review would be undertaken as part of the MIR process. Quality assurance - No tests are run as part of the package build process; however upstream do run these tests for all target series (12.04 - 14.04) prior to release so the overall quality of the codebase it pretty good. The package has some basic DEP-8 tests that bootstrap a local Juju environment to ensure everything hangs together OK. Dependencies juju-mongodb (see above) golang or gccgo TBC Currently all required go dependencies are snapshotted at specific upstream commits and bundled with Juju. Standards compliance OK Maintenance --- Upstream Juju team intend to manage stable point releases against the version shipped in 14.04. Ubuntu Server team will own the package in distro. Background information -- Some decisions still need to be made, mainly around toolchain. Specifically the aim is to support a single Go toolchain in Ubuntu main for all architectures; golang-go does not support arm64 or ppc64el yet, whereas the gccgo implementation does. Required changes to support gccgo have been upstreamed into the Juju codebase. Its also worth noting that the package and binaries in Ubuntu are used for: client tool (juju) juju agent (jujud) - but only for local provider and where --upload-tools is used Upstream released jujud binaries are/will be distributed officially via simplestreams using a documented build process (details TBC). The juju client will use these tools on public clouds and potentially in private cloud deployments where tools are synced into the cloud using the juju client tool (juju sync-tools). **
[Bug 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
I'd prefer to wait until the system is fully booted (traditional equivalent: rc2.d scripts are all complete), rather than just that startup scripts are done (traditional equivalent: rcS.d scripts are all complete). It doesn't seem to be that waiting for everything to be started would be much of an issue, if we could do it. And we might pre-empt some unusual bugs by more general assumptions being made by LXC consumers. -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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-1311-juju] Juju activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: SRU for juju-core 1.16.3 into saucy: DONE Work items for ubuntu-13.12: [doko] Provide 4.8.2 backport in PPA for Juju developers not running Trusty: DONE Create juju-mongodb package from mongodb: DONE [racb] Enable mongodb (core) on arm64: DONE [james-page] Enable juju-mongodb on arm64 and ppc64el: DONE Work items for ubuntu-14.01: [dave-cheney] Compatibility work juju-core - gccgo: DONE [dave-cheney] Backport fixes from 1.3 branch for the go tool: DONE [mwhudson] chase iant re: getting gccgo fixes into gcc 4.8 branch: DONE [dave-cheney] Work with upstream juju-core devs to switch to gccgo, at least for CI and landing: INPROGRESS - [james-page] Package go tool for use with gccgo: INPROGRESS + [james-page] Package go tool for use with gccgo: DONE [james-page] Upload 1.17.0 release with gccgo and gc built binaries: DONE [sinzui] Testing with gccgo in upstream CI: TODO Ensure no code duplication between gccgo and juju-core dependency bundle: DONE MIR raise juju-mongodb: DONE MIR raise juju-core: DONE MIR juju-core dependencies: TODO Work items for ubuntu-14.02: Testing of juju-core of gccgo early in cycle: INPROGRESS Update juju-core to next stable release: TODO MRE for juju-core: TODO Work items: Split shared go dependencies from juju-core source package: TODO Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED -- Juju activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju -- 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-1311-juju] Juju activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: SRU for juju-core 1.16.3 into saucy: DONE Work items for ubuntu-13.12: [doko] Provide 4.8.2 backport in PPA for Juju developers not running Trusty: DONE Create juju-mongodb package from mongodb: DONE [racb] Enable mongodb (core) on arm64: DONE [james-page] Enable juju-mongodb on arm64 and ppc64el: DONE Work items for ubuntu-14.01: [dave-cheney] Compatibility work juju-core - gccgo: DONE [dave-cheney] Backport fixes from 1.3 branch for the go tool: DONE [mwhudson] chase iant re: getting gccgo fixes into gcc 4.8 branch: DONE [dave-cheney] Work with upstream juju-core devs to switch to gccgo, at least for CI and landing: INPROGRESS [james-page] Package go tool for use with gccgo: DONE [james-page] Upload 1.17.0 release with gccgo and gc built binaries: DONE [sinzui] Testing with gccgo in upstream CI: TODO Ensure no code duplication between gccgo and juju-core dependency bundle: DONE MIR raise juju-mongodb: DONE MIR raise juju-core: DONE - MIR juju-core dependencies: TODO + MIR juju-core dependencies: INPROGRESS Work items for ubuntu-14.02: Testing of juju-core of gccgo early in cycle: INPROGRESS Update juju-core to next stable release: TODO MRE for juju-core: TODO Work items: Split shared go dependencies from juju-core source package: TODO Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED -- Juju activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju -- 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 1259203] Re: require versioned dependency on python-six
This bug was fixed in the package cinder - 1:2014.1~b2-0ubuntu1 --- cinder (1:2014.1~b2-0ubuntu1) trusty; urgency=low [ James Page ] * d/control: Add versioned dependency python-six = 1.4.1 (LP: #1259203). * d/p/*: Refreshed. [Chuck Short] * New upstream release. * debian/control: Add python-taskflow as a dependency. * debian/control: Add python-oslo.rootwrap as a dependency. -- Chuck Short zul...@ubuntu.com Thu, 23 Jan 2014 12:41:54 -0500 ** Changed in: cinder (Ubuntu) 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/1259203 Title: require versioned dependency on python-six To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1259203/+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 1271000] Re: lxc-start fails with Out of memory reading cgroups
Ah... now I understand... So this behavior is actually desirable. For example, to generate an empty rootfs when creating a new OS template or App template. This way the rootfs can be manually populated + tested before committing details to the template. Seems like having '-t none' might be good to roll into the code, so -t template is always required. Then when '-t none' is specified, maybe issue a simple informational message... something like... Creating container with an empty rootfs. Be sure to manually create rootfs to meet your needs. Or similar. Thanks for the info. This makes perfect sense now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1271000 Title: lxc-start fails with Out of memory reading cgroups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+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 1273484] Re: nagios-plugins renamed to monitoring-plugins
** Changed in: nagios-plugins (Ubuntu) Status: New = Triaged ** Changed in: nagios-plugins (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1273484 Title: nagios-plugins renamed to monitoring-plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1273484/+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 1271000] Re: lxc-start fails with Out of memory reading cgroups
Or maybe keep -t optional (so it works like always). And generate the informational message if -t is missing or '-t none' is specified. As more + more people use LXC, having this simple message seems like a life saver for newbies, like me. Thanks for the info. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1271000 Title: lxc-start fails with Out of memory reading cgroups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+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 1273654] Re: qemu-arm64-static binfmt registration for non-existent binary
Here's a patch for this issue. ** Patch added: 0001-Remove-the-arm64-binfmt-misc-entry-on-upgrade-since-.patch https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1273654/+attachment/3960650/+files/0001-Remove-the-arm64-binfmt-misc-entry-on-upgrade-since-.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1273654 Title: qemu-arm64-static binfmt registration for non-existent binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1273654/+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
Re: [Bug 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
FWIW, I just tried the following: sudo mknod /tmp/x1 sudo lxc-create -t ubuntu-cloud -n c1 sudo cat /var/lib/lxc/c1/config EOF lxc.mount.entry = /tmp/x1 x1 none bind,create=file 0 0 EOF sudo cat /var/lib/lxc/c1/rootfs/etc/init/x.conf EOF description tell lxc monitor we are ready author Serge Hallyn serge.hallyn@ubuntucom start on runlevel [2345] task script echo READY /x1 || true end script EOF Terminal 1: sudo tail -f /tmp/x1 Terminal 2: sudo lxc-start -n c1 READY showed up in my /tmp/x1 tail output as expected. So this should be a workable for what you want, to the point that I'm not sure whether something more generic is desirable. -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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
Re: [Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough
I'm sorry, this was the wrong bug! status: triaged ** Changed in: libvirt (Ubuntu) Status: Fix Released = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu mode = host- passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1262641/+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 1273689] [NEW] lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version
Public bug reported: Until 1.0.0beta2 I was using lxc-version command, beta3 seems to have dropped it, leaving no way to programatically query for it: * precise, saucy: $ lxc-version lxc version: 1.0.0.alpha1 $ lxc-cgroup --version [ ... ERROR ] * trusty (as of ~today): $ lxc-version lxc-version: command not found $ lxc-cgroup --version 1.0.0.beta3 Also note that lxc-version is still listed at: https://help.ubuntu.com/lts/serverguide/lxc.html ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/1273689 Title: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1273689/+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 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
I want it generic because I want adt-virt-lxc to work with any container it is given, without having to tell the user to set up a special container with special stuff in this special way. Other tools will want this too. I have a simple generic trusty container that I use to start-ephemeral (or clone, I suppose) whatever testing I need. Multiple tools can end up using this (adt-virt- lxc and perhaps eventually a uvt-lxc). They need to agree on a common way to achieve this common task; I think the suitable place for this to go is lxc. -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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
Re: [Bug 1273689] [NEW] lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version
Quoting JuanJo Ciarlante (1273...@bugs.launchpad.net): Public bug reported: Until 1.0.0beta2 I was using lxc-version command, beta3 seems to have dropped it, leaving no way to programatically query for it: You can use lxc-start --version to get that information. Also note that lxc-version is still listed at: https://help.ubuntu.com/lts/serverguide/lxc.html lxc-version is still in lts, but this will indeed need to be updated in the trusty serverguide before release. -- 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/1273689 Title: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1273689/+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
Re: [Bug 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
Quoting Robie Basak (1266...@bugs.launchpad.net): I want it generic because I want adt-virt-lxc to work with any container it is given, without having to tell the user to set up a special container with special stuff in this special way. Other tools will want this too. I have a simple generic trusty container that I use to start-ephemeral (or clone, I suppose) whatever testing I need. Multiple tools can end up using this (adt-virt- lxc and perhaps eventually a uvt-lxc). They need to agree on a common way to achieve this common task; I think the suitable place for this to go is lxc. Each distro+release guest would need to be updated using its own init system to inform us when the boot is complete, resulting in container-specific changes to the rootfs which is something we want to avoid. -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
In this millenium the concept of finished booting becomes more and more blurry anyway. We still have something like that with sysvinit if you do an rc2.d/S99_something, but with upstart/systemd/udev rules this already isn't accurate. To use the least common denominator we could have a late rc2.d sysvinit script do that, to notify callers that the container has booted sufficiently to have a working file system etc. This already won't guarantee us that the network is up (NetworkManager!) but any particular condition (wait for network, wait for ssh, etc.) that the lxc-wait caller expects can then be done using commands that you send to the container. So I think the initial wait until its safe to send files to the container and run commands in it provides a nice baseline which shouldn't be Debian specific if we use the runlevel/sysv approach from above. (Please keep in mind that this isn't just for autopkgtests, but that you can easily have e. g. a Fedora container on Ubuntu). -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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
Re: [Bug 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
On Tue, Jan 28, 2014 at 02:06:30PM -, Serge Hallyn wrote: Each distro+release guest would need to be updated using its own init system to inform us when the boot is complete, resulting in container-specific changes to the rootfs which is something we want to avoid. I understand your reasoning, but requiring tools that consume LXC to make these container-specific changes to the rootfs is worse; especially when there's one general concept that will need duplicated implementations across all consumers. You're just forcing the problem downstream, and the problem is exacerbated there. If you insist on not doing it this way, how about contrib style scripts, provided in the lxc package, which understands different init systems and arranges the wait mechanism? This would be a idempotently-modify-this-container-to-add-boot-wait command, with another boot-wait-on-the-container-i-modified command. Then at least the code will be in one place, and all consumers will use the same mechanism. A consumer would have to run the container modification script in between clone and container start (I assume this is possible). -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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 1007273] Re: autofs does not start automatically after reboot
Today I installed 12.04.4 and all the above fixes didn't work on a client machine. Even if in some other thread (i think bug 958704) this was discouraged, i added: start wait-for-state WAIT_FOR=ypbind WAITER=autofs WAIT_STATE=running after line 11 of /etc/init/autofs.conf, below the modprobe -q command. This is very bad of ubuntu, I am having nis problems since we started adopting it. I might consider going back to OpenSuSE. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/1007273 Title: autofs does not start automatically after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1007273/+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 1251237] Re: SpamAssassin's URI_OBFU_WWW rule claims www.tuning-net.ru is an obfuscated URL
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug should probably be fixed upstream, and then Ubuntu will pick it up. Have you considered testing the latest upstream release of spamassassin, and if affected then reporting the bug in the upstream spamassassin project? If you need a fix for an existing stable release of Ubuntu, please comment with a justification against https://wiki.ubuntu.com/StableReleaseUpdates#When and complete steps 1 through 4 in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure - and go ahead with all the steps if you can. Note that that SRU team would need to make a final decision, and that the bug needs to be fixed in the development version first - which would best happen via a new upstream release, or failing that a cherry-pick from an upstream commit. ** Changed in: spamassassin (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1251237 Title: SpamAssassin's URI_OBFU_WWW rule claims www.tuning-net.ru is an obfuscated URL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1251237/+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 1273429] Re: GNUCash won't open sqlite3 file due to libdbi
*** This bug is a duplicate of bug 1273407 *** https://bugs.launchpad.net/bugs/1273407 Thank you for taking the time to report this bug and helping to make Ubuntu better. Since this is the same issue as bug 1273407, I'll mark this as a duplicate and open a libdbi task there. ** This bug has been marked a duplicate of bug 1273407 won't open sqlite3 file due to libdbi -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libdbi in Ubuntu. https://bugs.launchpad.net/bugs/1273429 Title: GNUCash won't open sqlite3 file due to libdbi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbi/+bug/1273429/+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 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
Each distro+release guest would need to be updated using its own init system to inform us when the boot is complete LXC could provide a default implementation (like the above wait until runlevel switches to 2 and then notify the caller), and then templates could optionally provide a more refined version of that. I see nothing wrong with that, given that the notion of when is the container safe to work with seems quite universal? I see nothing wrong with putting that knowledge into the templates; that's pretty much exactly where it belongs to IMHO. -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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 1273407] Re: won't open sqlite3 file due to libdbi
Adding libdbi task to close duplicate bug. Does this make gnucash completely unusable? Does gnucash just need a rebuild against the latest libdbi? ** Also affects: libdbi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libdbi in Ubuntu. https://bugs.launchpad.net/bugs/1273407 Title: won't open sqlite3 file due to libdbi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1273407/+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 1273712] [NEW] jujud dies on ppc64el architecture
Public bug reported:
local provider bootstrapped ok:
juju status --debug
2014-01-28 15:02:33 INFO juju.provider.local environprovider.go:35 opening
environment local
2014-01-28 15:02:34 DEBUG juju state.go:75 waiting for DNS name(s) of state
server instances [localhost]
2014-01-28 15:02:34 INFO juju apiclient.go:118 state/api: dialing
wss://10.0.3.1:17070/
2014-01-28 15:02:34 INFO juju apiclient.go:128 state/api: connection established
environment: local
machines:
0:
agent-state: pending
dns-name: 10.0.3.1
instance-id: localhost
series: trusty
services: {}
2014-01-28 15:02:34 INFO juju.cmd supercommand.go:298 command finished
However the jujud process just keeps on exiting:
2014-01-28 15:00:39 INFO juju runner.go:262 worker: start authenticationworker
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:6,Type:Logger,Request:LoggingConfig,Params:{Entities:[{Tag:machine-0}]}}
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:7,Type:Provisioner,Request:Life,Params:{Entities:[{Tag:machine-0}]}}
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:109 - [1]
machine-0 8.777ms
{RequestId:4,Response:{Results:[{Life:alive,Error:null}]}}
Machiner[].Life
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:8,Type:KeyUpdater,Request:AuthorisedKeys,Params:{Entities:[{Tag:machine-0}]}}
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:9,Type:Machiner,Request:SetStatus,Params:{Entities:[{Tag:machine-0,Status:started,Info:,Data:null}],Machines:null}}
panic: runtime error: growslice: cap out of range [recovered]
panic: runtime error: growslice: cap out of range
goroutine 64 [running]:
bson.handleErr
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/bson.go:387
launchpad.net_juju_core_version.String.N38_launchpad.net_juju_core_version.Binary
/build/buildd/juju-core-1.17.0/src/launchpad.net/juju-core/version/version.go:75
launchpad.net_juju_core_version.GetBSON.N38_launchpad.net_juju_core_version.Binary
/build/buildd/juju-core-1.17.0/src/launchpad.net/juju-core/version/version.go:81
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:243
labix.org_v2_mgo_bson.addStruct.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:156
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:112
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:400
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:257
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:247
labix.org_v2_mgo_bson.addSlice.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:210
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:114
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:338
labix.org_v2_mgo_bson.addSlice.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:210
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:114
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:338
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:254
labix.org_v2_mgo_bson.addStruct.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:156
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:112
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:400
labix.org_v2_mgo_bson.addSlice.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:222
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:114
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/labix.org/v2/mgo/bson/encode.go:341
[Bug 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
Speaking as the upstream for LXC and package maintainer, the only way I consider to be acceptable for this is the one Serge and I described by adding a new socket owned by LXC which allows for a simple text based communication between the container and its host. This protocol would allow state ready kind of command which would allow switching to a list of allowed states that'd in turn be visible in lxc-wait. Monitoring the container's runlevel isn't practical as inotify isn't reliable, lxc-attach doesn't work on all kernels and containers may store that information on a filesystem we can't see from the host (e.g. /run on tmpfs) so I'll NACK any patch trying to implement something like this, both as an upstream change and as a distro-specific change. I've been fighting pretty hard this cycle to make sure LXC in Ubuntu is perfectly in sync with upstream, we don't carry any patches, our upstart jobs and apparmor profiles all come from upstream now, I'm not about to change this for this kind of hack, especially not when I'll have to maintain this for 5 years. We also have a policy in Ubuntu that LXC should not do any customization of the rootfs that'd be wrong to do on a host. So adding upstart jobs from the template is out of the question, any extra upstart jobs has to come through the distro (there again, we've been fighting to achieve this for years, I'm not about to compromise on this now). Note that in any case, this feature very likely won't make it before LXC 1.1 as I'm about to tag the first release candidate of LXC 1.0 after which point I won't be accepting feature changes anymore. -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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 1273712] Re: jujud dies on ppc64el architecture
** Attachment added: machine-0.log https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1273712/+attachment/3960716/+files/machine-0.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1273712 Title: jujud dies on ppc64el architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1273712/+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 1273689] Re: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version
Marking bug as invalid since there's a replacement command and our existing documentation is correct with regard to the version currently available in that release. ** Changed in: lxc (Ubuntu) Status: New = Invalid -- 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/1273689 Title: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1273689/+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 1273712] Re: jujud dies on ppc64el architecture
** Also affects: juju-core Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1273712 Title: jujud dies on ppc64el architecture To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273712/+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 1272196] Re: vmhgfs doesn't work with linux 3.13 kernel
Can you please provide logs, including dmesg, /etc/fstab, and other supporting evidence of this change? ** Changed in: open-vm-tools (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1272196 Title: vmhgfs doesn't work with linux 3.13 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1272196/+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 1273719] [NEW] netcf does not seem to handle source-directory directive in /etc/network/interfaces
Public bug reported: While doing some libvirt tests, I experienced errors executing any iface-* commands. After debugging, I found that libvirt uses netcf for these operations. I tracked the problem down to a source-directory line in my /etc/network/interfaces file. Once I removed that line, all the libvirt operations that relied on netcf seemed to work correctly. I am not sure what the specific package version is -- it was used to build libvirt from upstream sources. The build occurred on a saucy system. ** Affects: netcf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to netcf in Ubuntu. https://bugs.launchpad.net/bugs/1273719 Title: netcf does not seem to handle source-directory directive in /etc/network/interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1273719/+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 1129720] Re: juju instances not including the default security group
** Changed in: juju-core Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1129720 Title: juju instances not including the default security group To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1129720/+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 1273712] Re: jujud dies on ppc64el architecture
** Also affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1273712 Title: jujud dies on ppc64el architecture To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273712/+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-1311-openstack] Openstack Next Steps
Blueprint changed by Chuck Short: Work items changed: Work items for ubuntu-13.11: Setup Trusty Icehouse in Openstack-CI: DONE Setup Precise Icehouse in Openstack-CI: DONE Write MIR report for httpretty: INPROGRESS Write MIR report for mox3: INPROGRESS Setup staging PPA for precise icehouse: DONE Write MIR report for python-librabbitmq: DONE Write MIR report for librabbitmq: DONE Write MIR report beanstalkc: INPROGRESS Write MIR report for beanstalkd: INPROGRESS Porting of clients and oslo-incubator to python3: INPROGRESS Work items for ubuntu-13.12: [zulcss] Update libvirt to 1.2.0: INPROGRESS [zulcss] Package libvirt-python 1.2.0: DONE [zulcss] Sync packages from Trusty to Cloud Archive staging: DONE [zulcss] Package Trove for Ubuntu: DONE [zulcss] Package Savannah for Ubuntu: INPROGRESS Package Ironic for Ubuntu: TODO [zulcss] Package openstack icehouse-1: DONE [james-page] Neutron packaging review and deprecation of old-style plugins - ML2: DONE [james-page] Nova hypervisor packaging review and re-jig to support libvirt-less drivers: DONE [zulcss] Write MIR for mox3: DONE Porting of clients and oslo-incubator to python3: INPROGRESS [smb] MRE work for xen for Precise: DONE [smb] MRE work for xen for Raring: DONE [smb] MRE work for xen for Saucy: DONE [zulcss] Update oslo.messaging to 1.2.0~a11: DONE [zulcss] Package swift 1.11.0: DONE [zulcss] Write MIR for oslo.messaging: DONE [zulcss] Package oslo.rootwrap: DONE [zulcss] Package swift-bench: DONE [zulcss] Package python-designateclient: DONE [zulcss] Package python-workflow: DONE [zulcss] Package python-savannaclient: DONE [zulcss] Add versioned dependency for six for wsme: DONE [zulcss] Write MIR for oslo.rootwrap (#1259985): INPROGRESS [zulcss] Write MIR for python-pycadf (#1259984): INPROGRESS Work items for ubuntu-14.01: [zulcss] Update libvirt to 1.2.0: DONE [zulcss] Update libvirt to 1.2.1: DONE [zulcss] Update libvirt-python to 1.2.1: DONE [zulcss] Sync libvirt-python from Debian Unstable: DONE [zulcss] Write MIR for libvirt-python (#1262758): DONE [zulcss] Write MIR for oslo.rootwrap (#1259985): DONE [zulcss] Write MIR for python-pycadf (#1259984): DONE [james-page] Work out series upgrade with the juju-core team: INPROGRESS [zulcss] Package Savannah for Ubuntu: INPROGRESS [zulcss] Package savanna-extra for Ubuntu: INPROGRESS [zulcss] Package savanna-dashboard for Ubuntu: INPROGRESS [zulcss] Package savanaa-iamge-elements for Ubuntu: INPROGRESS [zulcss] Package python-manillaclient for Ubuntu: INPROGRESS [zulcss] Package manilla for Ubuntu: INPROGRESS [zulcss] Package python-savanaclient for Ubuntu: DONE [zulcss] Package swift 1.12.0: INPROGRESS [zulcss] Package Ironic for Ubuntu: DONE [zulcss] Package python-ironicclient: DONE [zulcss] Write MIR for Heat (#1267557): INPROGRESS [james-page] Monitor packaging for docker for Ubuntu/Debian: DONE [james-page] test docker.io (distro) on 14.04 (memcached tutorial tested): DONE [james-page] test lxc-docker (upstream) on 14.04 (memcached tutorial tested): DONE [zulcss] Write tools to integrate trusty testing upstream: INPROGRESS [zulcss] have non-voting ci-gate tests running on trusty: INPROGRESS [zulcss] Write tools to integrate libvirt-lxc testing upstream: INPROGRESS Discuss contribution of Juju/OpenStack documentation upstream (annegentle): TODO [zulcss] Package python-pyghmi: DONE [zulcss] Package openstack icehouse-2: DONE [zulcss] Prep cloud archive for icehouse-2: INPROGRESS - [zulcss] Write MIR for python-taskflow(#1271617): INPROGRESS - [zulcss] Write MIR for python-concurrent.futures (#1271606): INPROGRESS - [zulcss] Write MIR for python-networkx (#1271609): INPROGRESS + [zulcss] Write MIR for python-taskflow(#1271617): DONE + [zulcss] Write MIR for python-concurrent.futures (#1271606): DONE + [zulcss] Write MIR for python-networkx (#1271609): DONE Porting of clients and oslo-incubator to python3: INPROGRESS - Integrate trusty with devstack for 3rd party testing: TODO - Integrate libvirt-lxc with devstack for 3rd party testing: TODO + Integrate trusty with devstack for 3rd party testing: INPROGRESS + Integrate libvirt-lxc with devstack for 3rd party testing: INPROGRESS Work items for ubuntu-14.02: Write MIR for python-qpid: TODO Upgrade path testing and validation from precise-CA-trusty: TODO Package openstack icehouse-3: TODO Porting of clients and oslo-incubator to python3: INPROGRESS Work items for ubuntu-14.04: select and pull in appropriate xen version for trusty: INPROGRESS Make sure xen integration (xapi/libvirt/?) on openstack works: TODO Package openstack rc1: TODO Package openstack rc2: TODO Package openstack final release: TODO Porting of clients and oslo-incubator to python3: INPROGRESS -- Openstack Next Steps https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-openstack --
[Bug 1231970] Re: [FFe] nova-novncproxy requires websockify 0.5 - please sync from unstable
** Changed in: websockify (Ubuntu Trusty) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to websockify in Ubuntu. https://bugs.launchpad.net/bugs/1231970 Title: [FFe] nova-novncproxy requires websockify 0.5 - please sync from unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/websockify/+bug/1231970/+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 1273712] Re: jujud dies on ppc64el architecture
Switching to building with doko's preview 4.9 snapshot, this problem goes away, which points to a bug in the libgo runtime. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1273712 Title: jujud dies on ppc64el architecture To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273712/+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 1273654] Re: qemu-arm64-static binfmt registration for non-existent binary
** Branch linked: lp:ubuntu/trusty-proposed/qemu -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1273654 Title: qemu-arm64-static binfmt registration for non-existent binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1273654/+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 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+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-1311-cloud-images] cloud-images
Blueprint changed by Ben Howard: Work items changed: Work items for ubuntu-13.12: [james-page] File bug for openvswitch module move from extras to generic (bug 1253102): DONE [utlemming] EARLY- gpt partition table early: DONE [utlemming] EARLY- single image on ebs: TODO [sforshee] investigate Consolidation review for 'server' kernel to replace virtual for hardware and cloud: DONE - [utlemming] investigate size affect of btrfs and xfs support builtin to images: TODO + [utlemming] investigate size affect of btrfs and xfs support builtin to images: DONE [utlemming] investigate affect of having en_US.utf-8 locale pre-generated in images: TODO - [utlemming] investigate gpt partition table feasibility: TODO + [utlemming] investigate gpt partition table feasibility: DONE Work items for ubuntu-14.01: [smoser] document conversion of qcow2 to vmdk that works in vsphere and openstack: TODO [smoser] think about/test if zsync data is useful: TODO openvswitch module in linux-image (bug 1253102): DONE [smoser] dig more on 'server' kernel: TODO Work items for ubuntu-14.02: support for converting from qcow2 and uploading for vmware-openstack in example-sync: TODO -- cloud-images https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-cloud-images -- 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 1220950] Re: [MIR] open-vm-tools
Alright, good enough for libdumbnet. I'd still like to see its test suite fixed up and enabled. But if the cloud team is on top of things (and they are subbed to bugs), we'll be able to fix any problems. ** Changed in: libdumbnet (Ubuntu) Status: Incomplete = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1220950 Title: [MIR] open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdumbnet/+bug/1220950/+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 1062336] Re: nova-compute expects libvirtd group
Fixed in b2 upload for icehouse/trusty. ** Changed in: nova (Ubuntu Trusty) Status: Triaged = 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/1062336 Title: nova-compute expects libvirtd group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1062336/+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 1220950] Re: [MIR] open-vm-tools
Canonical's Cloudware team is confident that we can support libdumbnet. While it may have some rough edges, we have evaluated the package extensively. We will take ownership for issues related to this package. Additionally, libdumbnet is know at libdnet for SuSE/SLES and Fedora/Red Hat/Centos. For both all of those distributions, libdnet is a supported package; Fedora 19 and RHEL 7 beta include the libdnet as part of shipping open-vm-tools as a default. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1220950 Title: [MIR] open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdumbnet/+bug/1220950/+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 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
I just got hinted at lxc-attach. With that, clients like adt-virt-lxc can implement their own polling/waiting loop to wait until the runlevel switches away from unknown/S, which is a lot better (and more generic) than the current hackery that it's doing. I captured that in bug 1273725. -- 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/1266808 Title: No mechanism to wait until a started container is ready and has finished booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+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 1273654] Re: qemu-arm64-static binfmt registration for non-existent binary
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1273654 Title: qemu-arm64-static binfmt registration for non-existent binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1273654/+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 1273769] [NEW] ppc64el enablement for juju/lxc
Public bug reported: After some initial testing of juju (with local provider) on ppc64el - we need todo some work to fully enable this option. 1) LXC templates need to support ppc64el as a valid container arch 2) ubuntu-cloudimg-query is not avaliable on ppc64el 3) Juju is explicit in its support for x84 and arm - so enablement work is needed here as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta3-0ubuntu1 ProcVersionSignature: User Name 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic ppc64le ApportVersion: 2.13.2-0ubuntu2 Architecture: ppc64el Date: Tue Jan 28 16:49:03 2014 ProcEnviron: TERM=screen-256color-bce PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: juju-core Importance: Undecided Status: New ** Affects: cloud-utils (Ubuntu) Importance: Undecided Status: New ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ppc64el third-party-packages trusty uec-images ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-utils (Ubuntu) Importance: Undecided Status: New ** Also affects: juju-core Importance: Undecided Status: New -- 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/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+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 1224517] Re: please add glusterfs support
Maybe also worth to have a look at: https://bugs.launchpad.net/cloud- archive/+bug/1246924 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1224517 Title: please add glusterfs support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1224517/+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 1273769] Re: ppc64el enablement for juju/lxc
** Branch linked: lp:cloud-utils -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+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 1271857] Re: [MIR] ruby-rgen
This looks fine, thanks! Approved. ** Changed in: ruby-rgen (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ruby-rgen in Ubuntu. https://bugs.launchpad.net/bugs/1271857 Title: [MIR] ruby-rgen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-rgen/+bug/1271857/+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 1262692] Re: oops using openvswitch gre tunnels with upstream commit 703133de in kernel
** Tags removed: verification-done ** Tags added: verification-done-precise verification-done-quantal -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1262692 Title: oops using openvswitch gre tunnels with upstream commit 703133de in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1262692/+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 1273769] Re: ppc64el enablement for juju/lxc
** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+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 1224517] Re: please add glusterfs support
*** This bug is a duplicate of bug 1246924 *** https://bugs.launchpad.net/bugs/1246924 ** This bug has been marked a duplicate of bug 1246924 qemu not built with GlusterFS support -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1224517 Title: please add glusterfs support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1224517/+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 1251366] Re: [MIR] python-sure
python-sure no longer depends on python-steadymark so that task is invalid and this MIR should be reevaluated. python-sure (1.2.2-2) unstable; urgency=low * Drops dependency on python-steadymark (Closes: #722507). * Drops build-dependency on openstack-pkg-tools (and make it optional in debian/rules). -- Thomas Goirand z...@debian.org Wed, 04 Dec 2013 16:51:23 +0800 ** Changed in: python-steadymark (Ubuntu) Status: Incomplete = Invalid ** Changed in: python-steadymark (Ubuntu) Assignee: Chuck Short (zulcss) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-sure in Ubuntu. https://bugs.launchpad.net/bugs/1251366 Title: [MIR] python-sure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-steadymark/+bug/1251366/+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 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go
** Changed in: juju-core (Ubuntu) Status: Incomplete = New ** Description changed: gccgo-go Availability In universe, available on all required architectures (x86, armhf, arm64, ppc64el). Rationale - 'go' build tool built using gccgo, avoiding the need to promote two golang toolchains to Ubuntu main. Security Searching for golang CVE's turned up nothing (this package is a rename of the golang 1.2 source package). Quality assurance - Package installs cleanly, go tool installed using alternatives at higher priority that golang-go version in universe. Dependencies gccgo is in universe, all other dependencies in main. Standards compliance OK Maintenance --- Some bugs expected upfront but should stabilize before release. Probably picked up by ubuntu-server if foundations team don't want to. Background information -- This package is a re-cut of the golang upstream codebase with selected cherry-picks from upstream VCS for gccgo support, along with a patch to support building using gccgo + Make. The only code actually used is in src/cmd/go. juju-mongodb Availability In universe, available on all required architectures (x86, armhf, arm64, ppc64el). Rationale - MongoDB is a dependency for operating a Juju deployed Ubuntu environment. Security MongoDB has had some CVE's in the past, related to the use of the V8 and Spidermonkey Javascript engine in the Mongo Shell; however juju-mongodb builds without support for Javascript scripting, avoiding the historic CVE's (which where fixed upstream anyway). Quality assurance - Package installs cleanly, package build process runs upstream smoke tests (minus jstests due to disabling javascript support). Tests pass on all architectures. Dependencies All in main already Standards compliance OK (well is scons but we won't hold that against it) Maintenance --- Upstream MongoDB run stable releases with point updates; its intended that a MRE is applied for this package so point releases can be pushed as SRU's. Its also possible that we might need to bump a major version (2.4.x - 2.6.x); as this package is specific to Juju, we can constrain the impact and regression testing to Juju only. Background information -- Why a separate package? it was agreed at the last vUDS that having a separate package allows us to limit a) use of v8 (disabled) which was a security concern and b) allows us to potentially update at a later date if need be only impacting juju itself. juju-core Availability - In universe, not yet available on arm64 or ppc64el. + In universe. Rationale - Juju is the recommended service orchestration tool for Ubuntu; as such it really needs to be a core part of Ubuntu. Security No security history, but it was agreed that a security review would be undertaken as part of the MIR process. Quality assurance - No tests are run as part of the package build process; however upstream do run these tests for all target series (12.04 - 14.04) prior to release so the overall quality of the codebase it pretty good. The package has some basic DEP-8 tests that bootstrap a local Juju environment to ensure everything hangs together OK. Dependencies juju-mongodb (see above) - golang or gccgo TBC + gccgo + gccgo-go Currently all required go dependencies are snapshotted at specific upstream commits and bundled with Juju. Standards compliance OK Maintenance --- Upstream Juju team intend to manage stable point releases against the version shipped in 14.04. Ubuntu Server team will own the package in distro. Background information -- Some decisions still need to be made, mainly around toolchain. Specifically the aim is to support a single Go toolchain in Ubuntu main for all architectures; golang-go does not support arm64 or ppc64el yet, whereas the gccgo implementation does. Required changes to support gccgo have been upstreamed into the Juju codebase. Its also worth noting that the package and binaries in Ubuntu are used for: client tool (juju) juju agent (jujud) - but only for local provider and where --upload-tools is used Upstream released jujud binaries are/will be distributed officially via simplestreams using a documented build process (details TBC). The juju client will use these tools on public clouds and potentially in private cloud
[Bug 1220950] Re: [MIR] open-vm-tools
Override component to main libdumbnet 1.12-4 in trusty: universe/libs - main libdumbnet-dev 1.12-4 in trusty amd64: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty arm64: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty armhf: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty i386: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty powerpc: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty ppc64el: universe/libdevel/optional/100% - main libdumbnet1 1.12-4 in trusty amd64: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty arm64: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty armhf: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty i386: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty powerpc: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty ppc64el: universe/libs/optional/100% - main python-dumbnet 1.12-4 in trusty amd64: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty arm64: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty armhf: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty i386: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty powerpc: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty ppc64el: universe/python/optional/100% - main 19 publications overridden. ** Changed in: libdumbnet (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1220950 Title: [MIR] open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdumbnet/+bug/1220950/+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 1220950] Re: [MIR] open-vm-tools
Override component to main open-vm-tools 2:9.4.0-1280544-5ubuntu2 in trusty: universe/admin - main open-vm-dkms 2:9.4.0-1280544-5ubuntu2 in trusty amd64: universe/admin/extra/100% - main open-vm-dkms 2:9.4.0-1280544-5ubuntu2 in trusty arm64: universe/admin/extra/100% - main open-vm-dkms 2:9.4.0-1280544-5ubuntu2 in trusty armhf: universe/admin/extra/100% - main open-vm-dkms 2:9.4.0-1280544-5ubuntu2 in trusty i386: universe/admin/extra/100% - main open-vm-dkms 2:9.4.0-1280544-5ubuntu2 in trusty powerpc: universe/admin/extra/100% - main open-vm-dkms 2:9.4.0-1280544-5ubuntu2 in trusty ppc64el: universe/admin/extra/100% - main open-vm-toolbox 2:9.4.0-1280544-5ubuntu2 in trusty amd64: universe/admin/extra/100% - main open-vm-toolbox 2:9.4.0-1280544-5ubuntu2 in trusty arm64: universe/admin/extra/100% - main open-vm-toolbox 2:9.4.0-1280544-5ubuntu2 in trusty armhf: universe/admin/extra/100% - main open-vm-toolbox 2:9.4.0-1280544-5ubuntu2 in trusty i386: universe/admin/extra/100% - main open-vm-toolbox 2:9.4.0-1280544-5ubuntu2 in trusty powerpc: universe/admin/extra/100% - main open-vm-toolbox 2:9.4.0-1280544-5ubuntu2 in trusty ppc64el: universe/admin/extra/100% - main open-vm-tools 2:9.4.0-1280544-5ubuntu2 in trusty amd64: universe/admin/extra/100% - main open-vm-tools 2:9.4.0-1280544-5ubuntu2 in trusty i386: universe/admin/extra/100% - main open-vm-tools-dbg 2:9.4.0-1280544-5ubuntu2 in trusty amd64: universe/devel/extra/100% - main open-vm-tools-dbg 2:9.4.0-1280544-5ubuntu2 in trusty i386: universe/devel/extra/100% - main open-vm-tools-desktop 2:9.4.0-1280544-5ubuntu2 in trusty amd64: universe/admin/extra/100% - main open-vm-tools-desktop 2:9.4.0-1280544-5ubuntu2 in trusty i386: universe/admin/extra/100% - main open-vm-tools-dev 2:9.4.0-1280544-5ubuntu2 in trusty amd64: universe/devel/extra/100% - main open-vm-tools-dev 2:9.4.0-1280544-5ubuntu2 in trusty arm64: universe/devel/extra/100% - main open-vm-tools-dev 2:9.4.0-1280544-5ubuntu2 in trusty armhf: universe/devel/extra/100% - main open-vm-tools-dev 2:9.4.0-1280544-5ubuntu2 in trusty i386: universe/devel/extra/100% - main open-vm-tools-dev 2:9.4.0-1280544-5ubuntu2 in trusty powerpc: universe/devel/extra/100% - main open-vm-tools-dev 2:9.4.0-1280544-5ubuntu2 in trusty ppc64el: universe/devel/extra/100% - main open-vm-tools-dkms 2:9.4.0-1280544-5ubuntu2 in trusty amd64: universe/kernel/extra/100% - main open-vm-tools-dkms 2:9.4.0-1280544-5ubuntu2 in trusty arm64: universe/kernel/extra/100% - main open-vm-tools-dkms 2:9.4.0-1280544-5ubuntu2 in trusty armhf: universe/kernel/extra/100% - main open-vm-tools-dkms 2:9.4.0-1280544-5ubuntu2 in trusty i386: universe/kernel/extra/100% - main open-vm-tools-dkms 2:9.4.0-1280544-5ubuntu2 in trusty powerpc: universe/kernel/extra/100% - main open-vm-tools-dkms 2:9.4.0-1280544-5ubuntu2 in trusty ppc64el: universe/kernel/extra/100% - main 31 publications overridden. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1220950 Title: [MIR] open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdumbnet/+bug/1220950/+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 1273769] Re: ppc64el enablement for juju/lxc
(I have obviously no way of testing them, I'm expecting the lxc-ubuntu template to work fine and the lxc-ubuntu-cloud template to fail horribly due to missing images or missing support in ubuntu-cloudimg-query). -- 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/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+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 1273407] Re: won't open sqlite3 file due to libdbi
Does this make gnucash completely unusable? It affects all gnucash files stored as sqlite3. I would asume that due to libdbi1 it might also affect gnucash files stored in mysql or pgsql GNUCash xml files seem not to be affected. Tested opening of an existing gnucash xml, didn't test a new file Does gnucash just need a rebuild against the latest libdbi? This or a rebuild of libdbi (if build options of libdbi have changed) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libdbi in Ubuntu. https://bugs.launchpad.net/bugs/1273407 Title: won't open sqlite3 file due to libdbi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1273407/+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 1273712] Re: jujud dies on ppc64el architecture
** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1273712 Title: jujud dies on ppc64el architecture To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273712/+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 1273769] Re: ppc64el enablement for juju/lxc
I have sent patches enabling arm64 and ppc64el for both the ubuntu and ubuntu-cloud template, they should be in by the next 1.0 milestone (next week or so). -- 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/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+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 1031680] Re: check_apt always report 0 critical updates
Anyways ... please fill pull requests over there in https://github.com /monitoring-plugins/monitoring-plugins, the upstream has changed it's name. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/1031680 Title: check_apt always report 0 critical updates To manage notifications about this bug go to: https://bugs.launchpad.net/nagios-plugins/+bug/1031680/+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 1220950] Re: [MIR] open-vm-tools
Override component to main libdumbnet 1.12-4 in trusty: universe/libs - main libdumbnet-dev 1.12-4 in trusty amd64: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty arm64: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty armhf: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty i386: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty powerpc: universe/libdevel/optional/100% - main libdumbnet-dev 1.12-4 in trusty ppc64el: universe/libdevel/optional/100% - main libdumbnet1 1.12-4 in trusty amd64: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty arm64: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty armhf: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty i386: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty powerpc: universe/libs/optional/100% - main libdumbnet1 1.12-4 in trusty ppc64el: universe/libs/optional/100% - main python-dumbnet 1.12-4 in trusty amd64: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty arm64: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty armhf: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty i386: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty powerpc: universe/python/optional/100% - main python-dumbnet 1.12-4 in trusty ppc64el: universe/python/optional/100% - main 19 publications overridden. ** Changed in: open-vm-tools (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1220950 Title: [MIR] open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdumbnet/+bug/1220950/+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 1273689] Re: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version
FYI lxc-start --version fails on precise (and saucy), which then makes this check release dependent (and/or over existence of lxc-version binary). -- 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/1273689 Title: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1273689/+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 1273689] Re: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version
(sorry, early comment posting) - ie querying the version now cross releases would involve something alike: version=$((lxc-version 2/dev/null || lxc-start --version) | sed 's/.* //') That 'sed' is to cope with lxc-version textual formatting, while lxc- start --version shows it straight. -- 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/1273689 Title: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1273689/+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 1273825] [NEW] Curl module not activated after installation
Public bug reported: When installing php5-curl, the installation completes with succes, but module isn't activated ( no symlink created in /etc/php5/conf.d or /etc/php5/apache2/conf.d) So restarting/reloading apache doesn't reload curl module. If i manualy link curl.ini to conf.d, after apache restart, everything works as expected. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: php5-curl 5.5.3+dfsg-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Jan 28 20:38:09 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-03 (24 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=hr:en TERM=xterm PATH=(custom, no user) LANG=hr_HR.UTF-8 SHELL=/bin/bash SourcePackage: php5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa saucy third-party-packages -- 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/1273825 Title: Curl module not activated after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1273825/+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
Re: [Bug 1273712] Re: jujud dies on ppc64el architecture
oh dear, this is what I was afraid of
On Wed, Jan 29, 2014 at 5:45 AM, Curtis Hovey cur...@canonical.com wrote:
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
--
You received this bug notification because you are subscribed to juju-
core.
Matching subscriptions: MOAR JUJU SPAM!
https://bugs.launchpad.net/bugs/1273712
Title:
jujud dies on ppc64el architecture
Status in juju-core:
Triaged
Status in gcc-4.8 package in Ubuntu:
New
Status in juju-core package in Ubuntu:
New
Bug description:
local provider bootstrapped ok:
juju status --debug
2014-01-28 15:02:33 INFO juju.provider.local environprovider.go:35
opening environment local
2014-01-28 15:02:34 DEBUG juju state.go:75 waiting for DNS name(s) of
state server instances [localhost]
2014-01-28 15:02:34 INFO juju apiclient.go:118 state/api: dialing wss://
10.0.3.1:17070/
2014-01-28 15:02:34 INFO juju apiclient.go:128 state/api: connection
established
environment: local
machines:
0:
agent-state: pending
dns-name: 10.0.3.1
instance-id: localhost
series: trusty
services: {}
2014-01-28 15:02:34 INFO juju.cmd supercommand.go:298 command finished
However the jujud process just keeps on exiting:
2014-01-28 15:00:39 INFO juju runner.go:262 worker: start
authenticationworker
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:6,Type:Logger,Request:LoggingConfig,Params:{Entities:[{Tag:machine-0}]}}
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:7,Type:Provisioner,Request:Life,Params:{Entities:[{Tag:machine-0}]}}
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:109 - [1]
machine-0 8.777ms
{RequestId:4,Response:{Results:[{Life:alive,Error:null}]}}
Machiner[].Life
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:8,Type:KeyUpdater,Request:AuthorisedKeys,Params:{Entities:[{Tag:machine-0}]}}
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:9,Type:Machiner,Request:SetStatus,Params:{Entities:[{Tag:machine-0,Status:started,Info:,Data:null}],Machines:null}}
panic: runtime error: growslice: cap out of range [recovered]
panic: runtime error: growslice: cap out of range
goroutine 64 [running]:
bson.handleErr
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/bson.go:387
launchpad.net_juju_core_version.String.N38_launchpad.net_juju_core_version.Binary
/build/buildd/juju-core-1.17.0/src/
launchpad.net/juju-core/version/version.go:75
launchpad.net_juju_core_version.GetBSON.N38_launchpad.net_juju_core_version.Binary
/build/buildd/juju-core-1.17.0/src/
launchpad.net/juju-core/version/version.go:81
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:243
labix.org_v2_mgo_bson.addStruct.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:156
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:112
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:400
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:257
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:247
labix.org_v2_mgo_bson.addSlice.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:210
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:114
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:338
labix.org_v2_mgo_bson.addSlice.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:210
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:114
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:338
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:254
labix.org_v2_mgo_bson.addStruct.pN29_labix.org_v2_mgo_bson.encoder
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go
Doko, these seem up your alley ** Changed in: gccgo-go (Ubuntu) Assignee: (unassigned) = Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+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 1121874] Re: MySQL launch fails silently if 4MB of disk space is available
This bug was fixed in the package mysql-5.5 - 5.5.35-0ubuntu0.12.04.2 --- mysql-5.5 (5.5.35-0ubuntu0.12.04.2) precise; urgency=medium [ Eduardo Damato ] * Fix upstart script to account for datadir disk shortage (LP: #1121874) -- Dave Chiluk chi...@canonical.com Tue, 21 Jan 2014 13:11:07 -0500 ** Changed in: mysql-5.5 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1121874 Title: MySQL launch fails silently if 4MB of disk space is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+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 1121874] Re: MySQL launch fails silently if 4MB of disk space is available
This bug was fixed in the package mysql-5.5 - 5.5.35-0ubuntu0.12.10.2 --- mysql-5.5 (5.5.35-0ubuntu0.12.10.2) quantal; urgency=medium [ Eduardo Damato ] * Fix upstart script to account for datadir disk shortage (LP: #1121874) -- Dave Chiluk chi...@canonical.com Tue, 21 Jan 2014 13:09:30 -0500 ** Changed in: mysql-5.5 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: mysql-5.5 (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1121874 Title: MySQL launch fails silently if 4MB of disk space is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+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 1246098] Re: MIR: pollinate
** Changed in: pollen (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1246098 Title: MIR: pollinate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1246098/+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 1273877] Re: neutron-plugin-nicira should be renamed to neutron-plugin-vmware
I am happy to carry out the work if pointed in the right direction. Thanks, Armando -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1273877 Title: neutron-plugin-nicira should be renamed to neutron-plugin-vmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1273877/+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 1273877] [NEW] neutron-plugin-nicira should be renamed to neutron-plugin-vmware
Public bug reported: This is not a bug per se, but more like a feature request. As per: https://blueprints.launchpad.net/neutron/+spec/nicira-plugin-renaming During the Icehouse timeframe the Nicira NVP plugin is being renamed to VMware NSX plugin. Canonical's packages for Neutron should reflect that. ** Affects: neutron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1273877 Title: neutron-plugin-nicira should be renamed to neutron-plugin-vmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1273877/+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 1273689] Re: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version
So yes, if you want the upstream version number in a generic way which works with older and newer lxc, you'll need something like what you listed above. However, note that in most distributions, the upstream version number is mostly irrelevant due to the amount of cherry-picking that's done, The package version (dpkg -l lxc) tends to be much more reliable for that. In LXC's case, Ubuntu's 0.8 was very very close to the final 0.9 and 0.9 was also heavily patched to the point where it was almost identical to 1.0~alpha1, so only checking the upstream version likely won't give you what you want. With LXC 1.0, Ubuntu is going to be extremely close to what upstream offers, instead getting bugfixes releases done upstream rather than manually cherry-picking fixes, so that should limit the problem a bit, but still, checking for version usually isn't recommended. -- 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/1273689 Title: lxc-version is missing since 1.0.0beta3 - now lacking a programatic way to query lxc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1273689/+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 1250491] Re: pserv log is cluttered with tftp datagram received messages
To fix this we need a python-tx-tftp package refresh from upstream. ** Changed in: maas Status: New = Triaged ** Changed in: maas Milestone: None = 14.04 ** Also affects: python-tx-tftp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-tx-tftp in Ubuntu. https://bugs.launchpad.net/bugs/1250491 Title: pserv log is cluttered with tftp datagram received messages To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1250491/+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 1250491] Re: pserv log is cluttered with tftp datagram received messages
** Changed in: maas Assignee: (unassigned) = Andres Rodriguez (andreserl) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-tx-tftp in Ubuntu. https://bugs.launchpad.net/bugs/1250491 Title: pserv log is cluttered with tftp datagram received messages To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1250491/+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-1311-maas] MAAS activities for 14.04
Blueprint changed by Andres Rodriguez: Work items changed: Work items for ubuntu-13.12: [andreserl] Modify packaging to allow HA deployments without pulling unnecessary deps: DONE Work items for ubuntu-14.01: [andreserl] Charm maas-region: INPROGRESS - [andreserl] Charm maas-cluster: TODO + [andreserl] Charm maas-cluster: INPROGRESS Work items for ubuntu-14.02: [andreserl] UEFI Support: TODO [andreserl] Re-write maas-enlist in python and ship it with maas: TODO [andreserl] Make sure MAAS works flawlessly inside LXC: TODO [smoser] Simplestreams for hwe enablement: TODO -- MAAS activities for 14.04 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-maas -- 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 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
I have the exact same hang just trying to ssh into the host (remotely). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
The next time I removed the X forwarding ( ssh -X ) and it didn't hang so X-forwarding (or the attempted access thereof) may play a role in this bug. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1265544] Re: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7
Ok, I will send it on my next reboot.
For information, I was unable to suspend the laptop because it was awakening
some seconds later.
I made it working by using the following script (/etc/pm/sleep.d/20_zenbook) :
case ${1} in
hibernate|suspend)
# Unbind ehci_hcd for first device :00:14.0:
echo -n :00:14.0 | tee /sys/bus/pci/drivers/xhci_hcd/unbind
;;
resume|thaw)
# Bind ehci_hcd for first device :00:14.0:
echo -n :00:14.0 | tee /sys/bus/pci/drivers/xhci_hcd/bind
;;
esac
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265544
Title:
8086:0a16 [UX302LG] black screen on boot 3.12.0-7
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1265544/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
Quoting David Favor (da...@davidfavor.com): Correct. It appears the default template processing (default meaning no template specified) seems like it could use a bit of work. Ok, thanks. Seems like specifying no template should either throw an error or create some form of container that will start. For anyone reading this report who may not be clear on it, the current behavior is: a template exists to fill in a rootfs. If no template is specified, then it is assumed that a rootfs has already been created, and only the basic metadata (rootfs location etc) are to be filled in. People do rely on this behavior. So the question is how to best avoid the (more common imo) case where a user accidentally does not specify a template. We could force the existing no-template users to switch to specifying '-t none'. We could simply document the current behavior. We could print out a warning about there being no template, but not change the default behavior. Not sure if there are any other ideas. So the question is how to best handle this without causing trouble for people who rely on this default behavior. subject: change default template handling status: triaged importance: wishlist ** Changed in: libcgroup (Ubuntu) Importance: Undecided = Wishlist ** Changed in: libcgroup (Ubuntu) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271000 Title: lxc-start fails with Out of memory reading cgroups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273573] [NEW] missing key for update-notifier at upgrade
Public bug reported: When I do a sudo apt-get dist-upgrade on trusty, i get this notice : Processing triggers for libglib2.0-0:amd64 (2.39.3-0ubuntu4) ... Aucune clé nommée « auto-launch » dans le schéma « com.ubuntu.update-notifier » comme défini dans le fichier « /usr/share/glib-2.0/schemas/20_xubuntu-default-settings.gschema.override » de redéfinition; la redéfinition de cette clé a été ignorée. Processing triggers for libglib2.0-0:i386 (2.39.3-0ubuntu4) ... Aucune clé nommée « auto-launch » dans le schéma « com.ubuntu.update-notifier » comme défini dans le fichier « /usr/share/glib-2.0/schemas/20_xubuntu-default-settings.gschema.override » de redéfinition; la redéfinition de cette clé a été ignorée. ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** No longer affects: linuxmint -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273573 Title: missing key for update-notifier at upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1273573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273405] Re: Sync gthumb 3:3.3.1-1 (universe) from Debian experimental (main)
This bug was fixed in the package gthumb - 3:3.3.1-1 Sponsored for Jackson Doak (noskcaj) --- gthumb (3:3.3.1-1) experimental; urgency=medium [ Jackson Doak ] * New upstream release * Drop 25-fix_URL_in_About_and_copyright_year.patch, fixed upstream * Drop 13-fix_Close_mismatch.patch, not longer works * Add 14-unity_control_center.patch, use unity-control-center instead of gnome-control-center while in unity [ Yves-Alexis Perez ] * debian/control: - update libgtk-3-dev build-dep to 3.10. -- Jackson Doak nosk...@ubuntu.com Sat, 25 Jan 2014 11:24:27 +0100 ** Changed in: gthumb (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273405 Title: Sync gthumb 3:3.3.1-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1273405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273177] Re: useless message prefix for 2 upstart logs
Hi Jérôme - thank you for reporting this issue. However, this is not a bug in Upstart - Upstart simply records all output from the programs it starts, so that output is entirely up to the programs being run, not Upstart. The 2 examples you give do indeed prefix every line with their program name, which happens to match the name of the Upstart job, but there are many other jobs that do not do this. Upstart provides a logrotate script to ensure /var/log/upstart/*.log files get rotated and compressed. If you wish to silence the output from these 2 jobs, you can do so like this: echo console none| sudo tee /etc/init/container-detect.override echo console none| sudo tee /etc/init/ureadahead.override ** Changed in: upstart (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273177 Title: useless message prefix for 2 upstart logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1273177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244643] Re: [Novatech N1402 NNB-978] Touchpad does not work at all
Mailed linux-in...@vger.kernel.org with requested info. Re a url I cannot see it when I search http://www.spinics.net/lists /linux-input/ for Novatech touchpad but I suppose it takes a while to be put in there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244643 Title: [Novatech N1402 NNB-978] Touchpad does not work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232454] Re: Computer will suspend very soon because of inactivity. dialog when resuming from suspend
@ Ray Velez , I feel this is not a satisfying solution (I didn't try) because it is like a weakness in security settings. My script is not working well: although it works fine as long as the computer don't ends in sleep, when sleep happens then on resume then login the script won't do the job. I can't find why. Inactive-ScreenOff-Lock--Notify-Sleep-Resume-Login-KO (popup remains) Inactive-ScreenOff-Lock-Notify-Login-OK (close popup) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232454 Title: Computer will suspend very soon because of inactivity. dialog when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1232454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232454] Re: Computer will suspend very soon because of inactivity. dialog when resuming from suspend
@ Ray Velez , I feel this is not a satisfying solution (I didn't try) because it is like a weakness in security settings. My script is not working well: although it works fine as long as the computer don't ends in sleep, when sleep happens then on resume then login the script won't do the job. I can't find why. Inactive-ScreenOff-Lock-Notify-Sleep-Resume-Login-KO (popup remains) Inactive-ScreenOff-Lock-Notify-Login-OK (close popup) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232454 Title: Computer will suspend very soon because of inactivity. dialog when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1232454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273447] Re: samba sharing doesn't work on fresh Ubuntu 14.04 x64 build - net usershare add: cannot convert name Everyone to a SID. Access denied
*** This bug is a duplicate of bug 1261873 *** https://bugs.launchpad.net/bugs/1261873 ** This bug has been marked a duplicate of bug 1261873 'net usershare' returned error 255 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273447 Title: samba sharing doesn't work on fresh Ubuntu 14.04 x64 build - net usershare add: cannot convert name Everyone to a SID. Access denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1273447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244643] Re: [Novatech N1402 NNB-978] Touchpad does not work at all
I sent the mail from a normal (as far as I know it is like gmail) Google Apps email account but the mailer says the message containes HTML and has rejected it: Delivery to the following recipient failed permanently: linux-in...@vger.kernel.org Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the server for the recipient domain vger.kernel.org by vger.kernel.org. [209.132.180.67]. The error that the other server returned was: 550 5.7.1 Content-Policy reject msg: The message contains HTML subpart, therefore we consider it SPAM or Outlook Virus. TEXT/PLAIN is accepted.! BF:H 0; S1750983AbaA1ILz - Original message - X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=6VXe5YYXb95VHAzZ5B7URtKL476Wk1EevKHxEFKCc6U=; b=ge2ros0hU36q0LBlWwIPPbuDW0dA9dK9ymNFIAhUfRh6853Hicp3KAVKvNLLUIhOBs hUdKshonMxW2ntKUr1BChIRx+FersRltho0I/gfMuFVOdqMwG+LFXt/7WkMUnxnjmERf qfseXRzTYsz1ykfClH/60bX//Gvk03pvc2TbVttEPYGSew+lSlrKedye+Z+X2HH7wxuL qgY6CDW5ueYSCsRXEef7mNrXPozEE7xR6gMhWvbff+Hr9EHzkhXwFWDJ24vHasWoKm2b 9C7QlLmrpPwjP8P760B8d/5fl5ktE0ddHqrExlY//AVC+NIKaFjypJaC3rb/uxBJFk5F OyGQ== X-Gm-Message-State: ALoCoQnSHNRHUpFgjqyLIai0D5iqvdAFni26/REesPA6T2BqsYyA1t91xUj1ZgmyT+/qdpb4J0BX X-Received: by 10.224.88.3 with SMTP id y3mr208070qal.80.1390896714184; Tue, 28 Jan 2014 00:11:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.82.204 with HTTP; Tue, 28 Jan 2014 00:11:34 -0800 (PST) From: Geoff Kelsall a...@geoff.kelsall.name Date: Tue, 28 Jan 2014 10:11:34 +0200 Message-ID: CACwz48G76EJcVSS9Z=rbkkqfvoggponhokasyicew2fxqbp...@mail.gmail.com Subject: Touchpad does not work at all [Novatech N1402 NNB-978] To: linux-in...@vger.kernel.org Content-Type: multipart/alternative; boundary=001a11c3dbbc91906c04f103603a - Message truncated - But I cannot find the HTML in the message - which is: [Novatech N1402 NNB-978] Touchpad does not work at all WORKAROUND: Kernel parameter: i8042.noloop Linux version 3.13.0-031300-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201401192235 SMP Mon Jan 20 03:46:44 UTC 2014 Description:Ubuntu 12.04.2 LTS Release:12.04 geoff@geoff-laptop:/usr/src/linux-headers-3.13.0-031300/scripts$ sh ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux geoff-laptop 3.13.0-031300-generic #201401192235 SMP Mon Jan 20 03:46:44 UTC 2014 i686 i686 i386 GNU/Linux Gnu C 4.6 Gnu make 3.81 binutils 2.22 util-linux 2.20.1 mount support module-init-tools 3.16 e2fsprogs 1.42 pcmciautils018 PPP2.4.5 Linux C Library2.15 Dynamic linker (ldd) 2.15 Procps 3.2.8 Net-tools 1.60 Kbd1.15.2 Sh-utils 8.13 wireless-tools 30 Modules Loaded ctr ccm uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops promethean joydev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel psmouse snd_hda_codec serio_raw snd_hwdep arc4 snd_pcm rt2800pci snd_seq_midi rt2800mmio snd_rawmidi rt2800lib snd_seq_midi_event crc_ccitt i915 rt2x00mmio rt2x00pci rt2x00lib snd_seq mac80211 snd_timer snd_seq_device drm_kms_helper drm cfg80211 rfcomm snd bnep mac_hid lpc_ich i2c_algo_bit mei_me bluetooth parport_pc eeprom_93cx6 ppdev video mei soundcore snd_page_alloc binfmt_misc lp parport ahci libahci r8169 mii geoff@geoff-laptop:/usr/src/linux-headers-3.13.0-031300/scripts$ geoff@geoff-laptop:/usr/src/linux-headers-3.13.0-031300$ sh ver_linux sh: 0: Can't open ver_linux geoff@geoff-laptop:/usr/src/linux-headers-3.13.0-031300$ cd scripts/ geoff@geoff-laptop:/usr/src/linux-headers-3.13.0-031300/scripts$ sh ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux geoff-laptop 3.13.0-031300-generic #201401192235 SMP Mon Jan 20 03:46:44 UTC 2014 i686 i686 i386 GNU/Linux Gnu C 4.6 Gnu make 3.81 binutils 2.22 util-linux 2.20.1 mount support module-init-tools 3.16 e2fsprogs 1.42 pcmciautils018 PPP2.4.5 Linux C Library2.15 Dynamic linker (ldd) 2.15 Procps 3.2.8 Net-tools 1.60 Kbd1.15.2 Sh-utils 8.13 wireless-tools 30 Modules Loaded ctr ccm uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops promethean joydev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel psmouse snd_hda_codec serio_raw
