[Bug 1256546] Re: qemu-s390x-static: segmentation fault entering chroot
Version: 1.5.0+dfsg-3ubuntu5.2 This doesn't occur in version 1.5.0 in Saucy. Regression? The second stage fails anyway because it claims it cannot find /debootstrap/debootstrap which is similar to other open bugs, but there is no segfault. ** Tags added: regression-release -- 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/1256546 Title: qemu-s390x-static: segmentation fault entering chroot To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1256546/+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 1256546] Re: qemu-s390x-static: segmentation fault entering chroot
Does this patch fix this issue? http://patchwork.ozlabs.org/patch/309529/ -- 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/1256546 Title: qemu-s390x-static: segmentation fault entering chroot To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1256546/+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 1256546] Re: qemu-s390x-static: segmentation fault entering chroot
It certainly does! -- 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/1256546 Title: qemu-s390x-static: segmentation fault entering chroot To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1256546/+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 1269359] [NEW] package maas-region-controller 1.4+bzr1693+dfsg-0ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Setting up maas-region-controller (1.4+bzr1693+dfsg-0ubuntu2.2) ... Considering dependency proxy for proxy_http: Module proxy already enabled Module proxy_http already enabled Module expires already enabled Module wsgi already enabled sed: -e expression #1, char 89: unterminated `s' command dpkg: error processing maas-region-controller (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of maas: maas depends on maas-region-controller; however: Package maas-region-controller is not configured yet. dpkg: error processing maas (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of maas-dns: maas-dns depends on maas-region-controller (= 1.4+bzr1693+dfsg-0ubuntu2.2); however: Package maas-region-controller is not configured yet. dpkg: error processing maas-dns (--configure): dependency problems - leaving unconfigured Setting up google-chrome-stable (32.0.1700.77-1) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Could not parse file /usr/share/applications/idle.desktop: Key file does not start with a group Setting up flashplugin-installer (11.2.202.335ubuntu0.13.10.1) ... Processing triggers for libc-bin ... Processing triggers for menu ... Errors were encountered while processing: maas-region-controller maas maas-dns E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 13.10 Package: maas-region-controller 1.4+bzr1693+dfsg-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Wed Jan 15 17:31:53 2014 DuplicateSignature: package:maas-region-controller:1.4+bzr1693+dfsg-0ubuntu2.2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-11-02 (73 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MAASLog: MarkForUpload: True PackageArchitecture: all RelatedPackageVersions: python-django-maas 1.4+bzr1693+dfsg-0ubuntu2.2 apparmor 2.8.0-0ubuntu31.1 SourcePackage: maas Title: package maas-region-controller 1.4+bzr1693+dfsg-0ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1269359 Title: package maas-region-controller 1.4+bzr1693+dfsg-0ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1269359/+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] raise bug reports against gcc 4.8.2 that it gccgo is missing in the package: TODO [dave-cheney] Compatibility work juju-core - gccgo: DONE [dave-cheney] Backport fixes from 1.3 branch for the go tool: TODO [mwhudson] chase iant re: getting gccgo fixes into gcc 4.8 branch: TODO [dave-cheney] Work with upstream juju-core devs to switch to gccgo, at least for CI and landing: INPROGRESS Testing with gccgo in upstream CI: TODO - Testing of juju-core of gccgo early in cycle: TODO - Enable mongodb (v8) on arm64: TODO + Testing of juju-core of gccgo early in cycle: INPROGRESS + Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED Update juju-core to 2.x release: TODO Ensure no code duplication between gccgo and juju-core dependency bundle: TODO Split shared go dependencies from juju-core source package: TODO MIR raise juju-mongodb: DONE MIR raise juju-core: DONE MIR juju-core dependencies: TODO Work items for ubuntu-14.02: MRE for juju-core: TODO -- 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 1269073] Re: test_tomcat_daemon smoke test failure on images with 3.13 kernel
If the test @Robie suggests above resolves the issue it might indicate that this commit below (which was introduced to improve security) might be the underlying change which makes this worse: commit 40db23e5337d99fda05ee6cd18034b516f8f123d Author: Theodore Ts'o ty...@mit.edu Date: Sun Nov 3 00:15:05 2013 -0400 random: make add_timer_randomness() fill the nonblocking pool first Change add_timer_randomness() so that it directs incoming entropy to the nonblocking pool first if it hasn't been fully initialized yet. This matches the strategy we use in add_interrupt_randomness(), which allows us to push the randomness where we need it the most during when the system is first booting up, so that get_random_bytes() and /dev/urandom become safe to use as soon as possible. Signed-off-by: Theodore Ts'o ty...@mit.edu Note that i has been suggested that the machine does come up if you wait long enough. If we take the contention that this is indeed entropy related then if an init job hangs the system boot progress (preventing ssh etc) as it is waiting on entropy then all sources of entropy will also be gone other than network. This implies that if you ping the machine in this phase or increase the rate of ssh attempts that the machine might boot faster; which would also be confirmatory of this conjecture. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1269073 Title: test_tomcat_daemon smoke test failure on images with 3.13 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1269073/+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] raise bug reports against gcc 4.8.2 that it gccgo is missing in the package: TODO [dave-cheney] Compatibility work juju-core - gccgo: DONE [dave-cheney] Backport fixes from 1.3 branch for the go tool: TODO [mwhudson] chase iant re: getting gccgo fixes into gcc 4.8 branch: TODO [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 (faux): INPROGRESS Testing with gccgo in upstream CI: TODO Testing of juju-core of gccgo early in cycle: INPROGRESS Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED Update juju-core to 2.x release: TODO Ensure no code duplication between gccgo and juju-core dependency bundle: TODO Split shared go dependencies from juju-core source package: TODO MIR raise juju-mongodb: DONE MIR raise juju-core: DONE MIR juju-core dependencies: TODO Work items for ubuntu-14.02: MRE for juju-core: TODO -- 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 1268906] Re: cpu soft lockup running kvm
Alas, same issue using kernel 3.13.0-031300rc8-generic. ** Changed in: linux (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1256671] Re: Please merge lm-sensors 3.3.4 from debian
Merge uploaded. ** Changed in: lm-sensors (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1256671 Title: Please merge lm-sensors 3.3.4 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1256671/+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 1256671] Re: Please merge lm-sensors 3.3.4 from debian
** Branch linked: lp:~ubuntu-branches/ubuntu/trusty/lm-sensors/trusty- proposed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1256671 Title: Please merge lm-sensors 3.3.4 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1256671/+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 1262712] Re: [SRU] Backport iscsitarget 1.4.20.3+svn490 into Precise
Is it possible to backport only the needed fixes, not the whole snapshot? That will be much easier to review. Also, the description is missing a Regression Potential section. ** Also affects: iscsitarget (Ubuntu Precise) Importance: Undecided Status: New ** No longer affects: iscsitarget (Ubuntu) ** Changed in: iscsitarget (Ubuntu Precise) Status: New = Triaged ** Changed in: iscsitarget (Ubuntu Precise) Importance: Undecided = High ** Changed in: iscsitarget (Ubuntu Precise) Assignee: (unassigned) = Stefan Bader (smb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1262712 Title: [SRU] Backport iscsitarget 1.4.20.3+svn490 into Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/precise/+source/iscsitarget/+bug/1262712/+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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: maas (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
To workaround this issue: Change CIMC maas user permission from read-only from user. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1201029] Re: Please merge backuppc 3.3.0-1 (main) from Debian unstable (main)
sponsored for trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1201029 Title: Please merge backuppc 3.3.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1201029/+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 1201029] Re: Please merge backuppc 3.3.0-1 (main) from Debian unstable (main)
** Branch linked: lp:ubuntu/trusty-proposed/backuppc -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1201029 Title: Please merge backuppc 3.3.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1201029/+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 1269497] [NEW] Please upstream the AppArmor profiles
Public bug reported: Hello, It would be very nice if you could upstream the AppArmor profiles, so another distributions can use and contribute to them. Personally I would like to see this profiles on Debian. I asked the maintainer for inclusion of them, but he thinks that the profiles should be up-streamed first. Check http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706637 Thanks ** 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/1269497 Title: Please upstream the AppArmor profiles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1269497/+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 1256671] Re: Please merge lm-sensors 3.3.4 from debian
This bug was fixed in the package lm-sensors - 1:3.3.4-2ubuntu1 --- lm-sensors (1:3.3.4-2ubuntu1) trusty; urgency=low * Merge from Debian unstable (LP: #1256671). Remaining changes: - Add 100_recommend_using_upstart.patch: Recommend use of upstart rather than init-script. lm-sensors (1:3.3.4-2) unstable; urgency=low * debian/fancontrol.init: pass the config file location as argument of the fancontrol daemon (closes: #720213). lm-sensors (1:3.3.4-1) unstable; urgency=low * New upstream version. * Use dh-systemd to get proper systemd related maintainer scripts, based on a patch from Michael Stapelberg (closes: #714190). lm-sensors (1:3.3.3-1ubuntu1) saucy; urgency=low * Merge from Debian unstable (LP: #1178520). Remaining changes: - Add 100_recommend_using_upstart.patch: Recommend use of upstart rather than init-script. lm-sensors (1:3.3.3-1) unstable; urgency=low * New upstream version: - Don't choke on systems without PCI (closes: #695889). * Bumped Standards-version to 3.9.4.0 (no changes). * Compress .deb with xz. * Add a watch file (closes: #694848). * Fix RRD file creation with loadavg (closes: #614965). * Backport pwmconfig changes from upstream to fix multiple fan control (closes: #695895). -- Matt Fischer mfi...@ubuntu.com Mon, 02 Dec 2013 21:07:32 -0700 ** Changed in: lm-sensors (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1256671 Title: Please merge lm-sensors 3.3.4 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1256671/+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 1093918] Re: grub-probe auto-detection fails on raid
tested - OK ! *when will it be available?* there are only - as already mentioned some error messages a little ugly - but it works 2014/1/9 Josef Hope josef.klotz...@gmail.com Ok i will test in next days Am 09.01.2014 17:53 schrieb Phillip Susi ps...@ubuntu.com: The backport to precise is still waiting for someone to test and verify it, see comment #56. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid Status in “multipath-tools” package in Ubuntu: Fix Released Status in “multipath-tools” source package in Precise: Fix Committed Bug description: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. TEST CASE: Use fdisk to create an extended parition either on a fakeraid disk or an LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the partitions on the disk. Assuming the extended partition is number 3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the apparent size of the extended partition. The size should only be 2 sectors regardless of the size of the extended partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions -- Ing. Josef Klotzner -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+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 1201029] Re: Please merge backuppc 3.3.0-1 (main) from Debian unstable (main)
This bug was fixed in the package backuppc - 3.3.0-1ubuntu1 --- backuppc (3.3.0-1ubuntu1) trusty-proposed; urgency=low * Merge from Debian unstable. Remaining changes: (LP: #1201029) - debian/backuppc.init, debian/rules, debian/postinst: Do not call init script on shutdown and reboot (TearDown) (Closes: #488660). - debian/control: + Remove estraneous libtime-modules-perl (Closes: #734356). + Depend on default-mta | mail-transport-agent, instead of enumerating a long list of alternative MTAs. backuppc (3.3.0-1) unstable; urgency=low * New upstream release. Closes: #716824 * Fix Typo in kill signal name (ALRM vs ARLM). Closes: #698441 * Enable Apache2 (2.4) configuration by default. Closes: #718550 #710956 backuppc (3.2.1-5.2) unstable; urgency=low * Non-maintainer upload. * Patch BackupPC.pod for POD errors with Perl 5.18 pod2man has become more strict with perl 5.18. The applied patch converts the non-7-bit clean character into UTF-8 and declares the file's encoding as such. Thanks to Dominic Hargreaves d...@earth.li (Closes: #719827) backuppc (3.2.1-5.1) unstable; urgency=low * Non-maintainer upload. * Do not ship /etc/backuppc/config.pl as a conffile; it is handled by ucf already (Closes: #706315) backuppc (3.2.1-5) unstable; urgency=low * Added libtime-modules-perl dependency. Closes: #525395 * Remove /var/lib/backuppc/pc/localhost if it's empty Closes: #672372 * Added stuff to support Apache 2.4. Closes: #669765 * Added NICE support in /etc/default/backuppc. Closes: #639102 * Changed the default display date format. Closes: #663975 -- Louis Bouchard louis.bouch...@ubuntu.com Wed, 15 Jan 2014 09:33:13 -0600 ** Changed in: backuppc (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1201029 Title: Please merge backuppc 3.3.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1201029/+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 1263738] Re: login console 0 in user namespace container is not configured right
The same basic sequence of events happens with and without user
namespaces. init sheds its tty with setsid() but then opens
/dev/console, which as the effect of making /dev/console it's
controlling tty. Later getty also opens /dev/console and tries the
TIOCSCTTY ioctl on the fd. At this point I think the following code in
the kernel handling of that ioctl comes into play:
if (tty-session) {
/*
* This tty is already the controlling
* tty for another session group!
*/
if (arg == 1 capable(CAP_SYS_ADMIN)) {
/*
* Steal it away
*/
read_lock(tasklist_lock);
session_clear_tty(tty-session);
read_unlock(tasklist_lock);
} else {
ret = -EPERM;
goto unlock;
}
}
I.e. getty doesn't have CAP_SYS_ADMIN and thus can't steal the console
from init. I'm not sure what the fix is yet, whether there's something
we can do here which can allow root within a namespace to steal the
console or whether upstart just needs to explicitly shed the console
after opening it.
--
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/1263738
Title:
login console 0 in user namespace container is not configured right
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263738/+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 1093918] Re: grub-probe auto-detection fails on raid
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+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 1263738] Re: login console 0 in user namespace container is not configured right
Quoting Seth Forshee (seth.forshee...@canonical.com):
The same basic sequence of events happens with and without user
namespaces. init sheds its tty with setsid() but then opens
/dev/console, which as the effect of making /dev/console it's
controlling tty. Later getty also opens /dev/console and tries the
TIOCSCTTY ioctl on the fd. At this point I think the following code in
the kernel handling of that ioctl comes into play:
if (tty-session) {
/*
* This tty is already the controlling
* tty for another session group!
*/
if (arg == 1 capable(CAP_SYS_ADMIN)) {
/*
* Steal it away
*/
read_lock(tasklist_lock);
session_clear_tty(tty-session);
read_unlock(tasklist_lock);
} else {
ret = -EPERM;
goto unlock;
}
}
I.e. getty doesn't have CAP_SYS_ADMIN and thus can't steal the console
from init. I'm not sure what the fix is yet, whether there's something
we can do here which can allow root within a namespace to steal the
console or whether upstart just needs to explicitly shed the console
after opening it.
If it is possible to get to the inode backing the tty at this point
then we should be able to do inode_capable(tty_inode(tty),
CAP_SYS_ADMIN), which should be safe and adquate right?
But I dont' think we can get inode from tty. However we can get the
tty-session which is a struct pid*. So we can check whether we have
ns_capable(ns_of_pid(tty-session), CAP_SYS_ADMIN)
-serge
--
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/1263738
Title:
login console 0 in user namespace container is not configured right
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263738/+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: TODO + [andreserl] Charm maas-region: INPROGRESS [andreserl] Charm maas-cluster: TODO 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
[Blueprint servercloud-1311-maas] MAAS activities for 14.04
Blueprint changed by Patricia Gaughen: Definition Status: Drafting = Approved -- 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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
Yep, that was the workaround I used. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1263738] Re: login console 0 in user namespace container is not configured right
On Wed, Jan 15, 2014 at 06:37:41PM -, Serge Hallyn wrote:
If it is possible to get to the inode backing the tty at this point
then we should be able to do inode_capable(tty_inode(tty),
CAP_SYS_ADMIN), which should be safe and adquate right?
But I dont' think we can get inode from tty. However we can get the
I'm new to how capabilities are handled with user namespaces, but at a
glance I think inode_capable() looks sufficient. We can't get the inode
from the tty but it could easily be passed as an argument the function
containing that code.
tty-session which is a struct pid*. So we can check whether we have
ns_capable(ns_of_pid(tty-session), CAP_SYS_ADMIN)
Except that we're not interested in the capabilities of tty-session but
of current since current is the one doing the stealing. So that should
probably be ns_capable(current_user_ns(), CAP_SYS_ADMIN).
I'm thinking though we also need to verify that tty-session is in the
same namespace, otherwise nothing seems to prevent a lesser priveleged
namespace from doing mknod and stealing any tty from another namespace,
which seems like a serious security issue. So something along the lines
of:
if (arg == 1
(capable(CAP_SYS_ADMIN) ||
(current_user_namespace() == ns_of_pid(tty-session)
ns_capable(current_user_ns(), CAP_SYS_ADMIN {
/* steal tty */
}
Or am I being too paranoid?
--
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/1263738
Title:
login console 0 in user namespace container is not configured right
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263738/+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 1263738] Re: login console 0 in user namespace container is not configured right
Quoting Seth Forshee (seth.forshee...@canonical.com):
On Wed, Jan 15, 2014 at 06:37:41PM -, Serge Hallyn wrote:
If it is possible to get to the inode backing the tty at this point
then we should be able to do inode_capable(tty_inode(tty),
CAP_SYS_ADMIN), which should be safe and adquate right?
But I dont' think we can get inode from tty. However we can get the
I'm new to how capabilities are handled with user namespaces, but at a
glance I think inode_capable() looks sufficient. We can't get the inode
from the tty but it could easily be passed as an argument the function
containing that code.
The question actually remains: what do we need privilege toward? If
user A has file F open, and we are going to steal F from A... IIUC we
already should have check for permission to access F right? So now the
question is only whether we can take something from A, or whether A is
more privileged than us.
tty-session which is a struct pid*. So we can check whether we have
ns_capable(ns_of_pid(tty-session), CAP_SYS_ADMIN)
Except that we're not interested in the capabilities of tty-session but
The ns_capable line doesn't check the capabilities of tty-session,
but rather current's capabilities targeted toward the user namespace
which owns tty-session.
of current since current is the one doing the stealing. So that should
probably be ns_capable(current_user_ns(), CAP_SYS_ADMIN).
That would check the privilege of current toward his own userns. Any
unprivileged user can clone(CLONE_NEWUSER) and have that test evaluate
to true.
I'm thinking though we also need to verify that tty-session is in the
same namespace, otherwise nothing seems to prevent a lesser priveleged
namespace from doing mknod and stealing any tty from another namespace,
which seems like a serious security issue. So something along the lines
of:
if (arg == 1
(capable(CAP_SYS_ADMIN) ||
(current_user_namespace() == ns_of_pid(tty-session)
ns_capable(current_user_ns(), CAP_SYS_ADMIN {
/* steal tty */
}
Or am I being too paranoid?
That would be the point of doing:
ns_capable(ns_of_pid(tty-session), CAP_SYS_ADMIN)
If you are in a child userns of init, you cannot CAP_SYS_ADMIN toward
init's pidns.
--
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/1263738
Title:
login console 0 in user namespace container is not configured right
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263738/+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 1263738] Re: login console 0 in user namespace container is not configured right
On Wed, Jan 15, 2014 at 07:53:54PM -, Seth Forshee wrote:
On Wed, Jan 15, 2014 at 06:37:41PM -, Serge Hallyn wrote:
If it is possible to get to the inode backing the tty at this point
then we should be able to do inode_capable(tty_inode(tty),
CAP_SYS_ADMIN), which should be safe and adquate right?
But I dont' think we can get inode from tty. However we can get the
I'm new to how capabilities are handled with user namespaces, but at a
glance I think inode_capable() looks sufficient. We can't get the inode
from the tty but it could easily be passed as an argument the function
containing that code.
tty-session which is a struct pid*. So we can check whether we have
ns_capable(ns_of_pid(tty-session), CAP_SYS_ADMIN)
Except that we're not interested in the capabilities of tty-session but
of current since current is the one doing the stealing. So that should
probably be ns_capable(current_user_ns(), CAP_SYS_ADMIN).
I'm thinking though we also need to verify that tty-session is in the
same namespace, otherwise nothing seems to prevent a lesser priveleged
namespace from doing mknod and stealing any tty from another namespace,
which seems like a serious security issue. So something along the lines
of:
if (arg == 1
(capable(CAP_SYS_ADMIN) ||
(current_user_namespace() == ns_of_pid(tty-session)
ns_capable(current_user_ns(), CAP_SYS_ADMIN {
/* steal tty */
}
Or am I being too paranoid?
mknod isn't possible from a userns, otherwise we'd be in a lot more
problem than just tty devices (think what would hapeen if I could mknod
sda in a container).
--
You received this bug notification because you are subscribed to lxc in
Ubuntu.
Matching subscriptions: containers
https://bugs.launchpad.net/bugs/1263738
Title:
login console 0 in user namespace container is not configured right
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263738/+subscriptions
--
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
--
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/1263738
Title:
login console 0 in user namespace container is not configured right
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263738/+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 1263738] Re: login console 0 in user namespace container is not configured right
On Wed, Jan 15, 2014 at 08:18:04PM -, Serge Hallyn wrote: The ns_capable line doesn't check the capabilities of tty-session, but rather current's capabilities targeted toward the user namespace which owns tty-session. Okay, this was my fundamental misunderstanding. It makes sense now. This plus the fact that mknod isn't allowed from a user ns alleviates my concerns. I'll try this out. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1263738 Title: login console 0 in user namespace container is not configured right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263738/+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 1268050] Re: Deprovision breaks iDNS registration when using cloud-init
Due to the EOL for Ubuntu 13.04 on January 27th, I am only going to SRU this back to 12.04 and 13.10. ** Also affects: walinuxagent (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: walinuxagent (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: walinuxagent (Ubuntu Trusty) Importance: Medium Assignee: Ben Howard (utlemming) Status: Confirmed ** Changed in: walinuxagent (Ubuntu Saucy) Assignee: (unassigned) = Ben Howard (utlemming) ** Changed in: walinuxagent (Ubuntu Precise) Assignee: (unassigned) = Ben Howard (utlemming) ** Changed in: walinuxagent (Ubuntu Saucy) Milestone: None = saucy-updates ** Changed in: walinuxagent (Ubuntu Precise) Milestone: None = precise-updates ** Changed in: walinuxagent (Ubuntu Precise) Status: New = In Progress ** Changed in: walinuxagent (Ubuntu Saucy) Status: New = In Progress ** Changed in: walinuxagent (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: walinuxagent (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: walinuxagent (Ubuntu Saucy) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1268050 Title: Deprovision breaks iDNS registration when using cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1268050/+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 1268050] Re: Deprovision breaks iDNS registration when using cloud-init
** Description changed: + SRU justification + + Impact : Users who run waagent --deprovision and then capture/snapshot + an image will not have the instance register with iDNS and subsiquently + the instance will be unreachable. + + This issue is caused by waagent changing the send-hostname parameter + in the dhclient. + + Fix : Applied upstream commit from + https://github.com/WindowsAzure/WALinuxAgent/commit/375f1ede38fd323c2560e7e21ba99ac50bc66acd + + Test Case : + - Launch instance + - Install walinuxagent from proposed + - Run waagent --deprovision + - Shutdown instance + - Run azure vm shutdown name with Azure CLI tool + - Run azure vm capture name new name with Azure CLI tool + - Launch new instance from new name + - Confirm that instance is accesable using DNS name + + Regression : Low. The change fixes how waagent interacts with + /etc/dhcp/dhcpclient.conf. If an instance has been configured via cloud- + init, there is no change. + + [ORIGNIAL BUG REPORT] Hello, This is a request to please backport this patch from the 1.4.1 agent: https://github.com/WindowsAzure/WALinuxAgent/commit/375f1ede38fd323c2560e7e21ba99ac50bc66acd - Summary The Ubuntu images in the Windows Azure gallery (except for 12.10) all use cloud-init for provisioning. This means that WALA provisioning and the hostname monitor are disabled via /etc/waagent.conf. However, when a user runs 'waagent -deprovision' the agent will attempt to modify the 'send host-name' parameter dhclient.conf file to set the hostname to localhost.localdomain. But with provisioning and the monitor disabled, the agent does not have a chance to reset this parameter to the proper hostname. So captured Ubuntu images will not register their correct DNS name with the DHCP server. In the Ubuntu images this behavior is not necessary since dhclient is already configured to send its hostname to the DHCP server. This patch makes the agent a bit smarter about this and leaves dhclient.conf alone if it sees that it is already configured to send it's current hostname to the DHCP server. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1268050 Title: Deprovision breaks iDNS registration when using cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1268050/+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 1269626] Re: cloud-init uses incorrect GUID for instance ID
Log snip showing end of first boot and second boot. fig_power_state_change - wb: [420] 20 bytes Jan 15 20:09:31 utl-0115-lp1268050 [CLOUDINIT] helpers.py[DEBUG]: Running config-power-state-change using lock (FileLock using file '/var/ lib/cloud/instances/9becc63a498847de99d6961c7ae0a95f/sem/config_power_state_change') Jan 15 20:09:31 utl-0115-lp1268050 [CLOUDINIT] cc_power_state_change.py[DEBUG]: no power_state provided. doing nothing Jan 15 20:09:31 utl-0115-lp1268050 [CLOUDINIT] cloud-init[DEBUG]: Ran 10 modules with 0 failures Jan 15 20:09:31 utl-0115-lp1268050 [CLOUDINIT] util.py[DEBUG]: Reading from /proc/uptime (quiet=False) Jan 15 20:09:31 utl-0115-lp1268050 [CLOUDINIT] util.py[DEBUG]: Read 11 bytes from /proc/uptime Jan 15 20:09:31 utl-0115-lp1268050 [CLOUDINIT] util.py[DEBUG]: cloud-init mode 'modules' took 0.407 seconds (0.41) 2014-01-15 21:52:19,552 - util.py[DEBUG]: Cloud-init v. 0.7.5 running 'init-local' at Wed, 15 Jan 2014 21:52:19 +. Up 22.39 seconds. 2014-01-15 21:52:19,668 - util.py[DEBUG]: Writing to /var/log/cloud-init.log - ab: [420] 0 bytes 2014-01-15 21:52:19,669 - util.py[DEBUG]: Changing the ownership of /var/log/cloud-init.log to 101:4 2014-01-15 21:52:19,669 - util.py[DEBUG]: Attempting to remove /var/lib/cloud/instance/boot-finished 2014-01-15 21:52:19,670 - util.py[DEBUG]: Attempting to remove /var/lib/cloud/instance 2014-01-15 21:52:19,670 - util.py[DEBUG]: Attempting to remove /var/lib/cloud/data/no-net 2014-01-15 21:52:19,670 - util.py[DEBUG]: Reading from /var/lib/cloud/instance/obj.pkl (quiet=False) 2014-01-15 21:52:19,672 - importer.py[DEBUG]: Looking for modules ['ubuntu', 'cloudinit.distros.ubuntu'] that have attributes ['Distro'] 2014-01-15 21:52:19,672 - importer.py[DEBUG]: Failed at attempted import of 'ubuntu' due to: No module named ubuntu 2014-01-15 21:52:19,720 - importer.py[DEBUG]: Found ubuntu with attributes ['Distro'] in ['cloudinit.distros.ubuntu'] 2014-01-15 21:52:19,721 - stages.py[DEBUG]: Using distro class class 'cloudinit.distros.ubuntu.Distro' 2014-01-15 21:52:19,721 - __init__.py[DEBUG]: Looking for for data source in: ['Azure'], via packages ['', 'cloudinit.sources'] that matche s dependencies ['FILESYSTEM'] 2014-01-15 21:52:19,721 - importer.py[DEBUG]: Looking for modules ['DataSourceAzure', 'cloudinit.sources.DataSourceAzure'] that have attrib utes ['get_datasource_list'] 2014-01-15 21:52:19,721 - importer.py[DEBUG]: Failed at attempted import of 'DataSourceAzure' due to: No module named DataSourceAzure 2014-01-15 21:52:19,965 - importer.py[DEBUG]: Found DataSourceAzure with attributes ['get_datasource_list'] in ['cloudinit.sources.DataSour ceAzure'] 2014-01-15 21:52:19,965 - __init__.py[DEBUG]: Searching for data source in: [] 2014-01-15 21:52:19,965 - cloud-init[DEBUG]: No local datasource found 2014-01-15 21:52:19,966 - util.py[DEBUG]: Reading from /proc/uptime (quiet=False) 2014-01-15 21:52:19,966 - util.py[DEBUG]: Read 11 bytes from /proc/uptime 2014-01-15 21:52:19,966 - util.py[DEBUG]: cloud-init mode 'init' took 0.594 seconds (0.59) ** Description changed: Upon 'capturing' a Ubuntu VM on Windows Azure, instances do not come up. - This is caused by Azure re-using the wrong GUID. + It appears that the cause is that Cloud-init is not looking at any + datasources. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cloud-init 0.7.5~bzr902-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Wed Jan 15 22:29:49 2014 PackageArchitecture: all SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - cloud-init uses incorrect GUID for instance ID + cloud-init Azure Datasource does not detect new instance -- 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/1269626 Title: cloud-init Azure Datasource does not detect new instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+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 1269626] [NEW] cloud-init Azure Datasource does not detect new instance
Public bug reported: Upon 'capturing' a Ubuntu VM on Windows Azure, instances do not come up. It appears that the cause is that Cloud-init is not looking at any datasources. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cloud-init 0.7.5~bzr902-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Wed Jan 15 22:29:49 2014 PackageArchitecture: all SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Medium Assignee: Ben Howard (utlemming) Status: In Progress ** Tags: amd64 apport-bug trusty uec-images ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) = Ben Howard (utlemming) ** Changed in: cloud-init (Ubuntu) Importance: Undecided = Medium ** Changed in: cloud-init (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1269626 Title: cloud-init Azure Datasource does not detect new instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+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 1269626] Re: cloud-init Azure Datasource does not detect new instance
** Attachment added: Cloud-init log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+attachment/3949810/+files/cloud-init.log -- 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/1269626 Title: cloud-init Azure Datasource does not detect new instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+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 1269626] Re: cloud-init Azure Datasource does not detect new instance
Confirmed that this happening in Saucy too. $ ssh utlemm...@utl-0115-utl-0115-s1-a1.cloudapp.net ssh: connect to host utl-0115-utl-0115-s1-A1.cloudapp.net port 22: Connection refused ssh: connect to host utl-0115-utl-0115-s1-A1.cloudapp.net port 22: Connection refused -- 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/1269626 Title: cloud-init Azure Datasource does not detect new instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+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 1269626] Re: cloud-init Azure Datasource does not detect new instance
Cloud-init log for above comment ** Attachment added: cloud-init.log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+attachment/3949827/+files/cloud-init.log -- 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/1269626 Title: cloud-init Azure Datasource does not detect new instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+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 1269626] Re: cloud-init Azure Datasource does not detect new instance
Here is a diff between the SharedConfig.xml, with cloud-init.log as an
attachment
--- waagent.pre/SharedConfig.xml2014-01-15 22:46:09.619537000 +
+++ waagent/SharedConfig.xml2014-01-15 22:54:33.606734299 +
@@ -1,32 +1,32 @@
?xml version=1.0 encoding=utf-8?
SharedConfig version=1.0.0.0 goalStateIncarnation=1
- Deployment name=ba5ce29e7b4d435f8d70ed5b7c471875
guid={71d37c98-32e5-4627-a9c7-7498c603ed50} incarnation=0
-Service name=utl-0115-s1 guid={----}
/
-ServiceInstance name=ba5ce29e7b4d435f8d70ed5b7c471875.0
guid={c63183ea-1284-426b-a288-6af3f7397a36} /
+ Deployment name=fd9cfa887ac24eeab7efc8e5b48d799a
guid={5fcccddd-25c5-47c1-9ed0-2c37ab5a8612} incarnation=0
+Service name=utl-0115-utl-0115-s1-A1
guid={----} /
+ServiceInstance name=fd9cfa887ac24eeab7efc8e5b48d799a.0
guid={a610f152-aa8f-492e-82bc-053384ea88dd} /
/Deployment
- Incarnation number=1 instance=utl-0115-s1
guid={07230d59-14a8-446a-9e2c-893250c47407} /
- Role guid={692f906f-115d-e08d-2178-90db611dc71b} name=utl-0115-s1
settleTimeSeconds=0 /
+ Incarnation number=1 instance=utl-0115-utl-0115-s1-A1
guid={7ef9d281-0865-459c-a1aa-4acf1f10123a} /
+ Role guid={04c0d2f4-1503-977c-d3f7-408268609c71}
name=utl-0115-utl-0115-s1-A1 settleTimeSeconds=0 /
LoadBalancerSettings timeoutSeconds=0 waitLoadBalancerProbeCount=8
Probes
Probe name=D41D8CD98F00B204E9800998ECF8427E /
- Probe name=AEEC72A7AAC0423C26FCB170FD1035DA /
+ Probe name=B295630DB75FB8FCBC300D7E1500940F /
/Probes
/LoadBalancerSettings
OutputEndpoints
-Endpoint name=utl-0115-s1:openInternalEndpoint type=SFS
- Target instance=utl-0115-s1 endpoint=openInternalEndpoint /
+Endpoint name=utl-0115-utl-0115-s1-A1:openInternalEndpoint type=SFS
+ Target instance=utl-0115-utl-0115-s1-A1
endpoint=openInternalEndpoint /
/Endpoint
/OutputEndpoints
Instances
-Instance id=utl-0115-s1 address=100.92.36.21
+Instance id=utl-0115-utl-0115-s1-A1 address=100.92.38.42
FaultDomains randomId=0 updateId=0 updateCount=0 /
InputEndpoints
-Endpoint name=openInternalEndpoint address=100.92.36.21
protocol=any isPublic=false enableDirectServerReturn=false
isDirectAddress=false disableStealthMode=false
+Endpoint name=openInternalEndpoint address=100.92.38.42
protocol=any isPublic=false enableDirectServerReturn=false
isDirectAddress=false disableStealthMode=false
LocalPorts
LocalPortSelfManaged /
/LocalPorts
/Endpoint
-Endpoint name=ssh address=100.92.36.21:22 protocol=tcp
hostName=utl-0115-s1ContractContract isPublic=true
loadBalancedPublicAddress=191.235.134.61:22 enableDirectServerReturn=false
isDirectAddress=false disableStealthMode=false
+Endpoint name=ssh address=100.92.38.42:22 protocol=tcp
hostName=utl-0115-utl-0115-s1-A1ContractContract isPublic=true
loadBalancedPublicAddress=191.235.132.109:22 enableDirectServerReturn=false
isDirectAddress=false disableStealthMode=false
LocalPorts
LocalPortRange from=22 to=22 /
/LocalPorts
--
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/1269626
Title:
cloud-init Azure Datasource does not detect new instance
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+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 1269626] Re: cloud-init Azure Datasource does not detect new instance
From Saucy instance, here is walinuxagent's /var/lib/waagent/waagent.log Cloud-init is using ba5ce29e7b4d435f8d70ed5b7c471875 as the instance ID, but that instance ID is not unique when a machine is captured. 2014/01/12 08:12:30 Configured SSH client probing to keep connections alive. 2014/01/15 22:44:47 Windows Azure Linux Agent Version: WALinuxAgent-1.3.2 2014/01/15 22:44:47 Linux Distribution Detected : Ubuntu 2014/01/15 22:44:47 IPv4 address: 100.92.36.21 2014/01/15 22:44:47 MAC address: 00:15:5D:86:BE:4D 2014/01/15 22:44:47 Probing for Windows Azure environment. 2014/01/15 22:44:48 DoDhcpWork: Setting socket.timeout=10, entering recv 2014/01/15 22:44:48 Discovered Windows Azure endpoint: 100.92.36.60 2014/01/15 22:44:48 WARNING:Newer wire protocol version detected. Please consider updating waagent. 2014/01/15 22:44:48 Negotiated wire protocol version: 2011-12-31 2014/01/15 22:44:48 Retrieved GoalState from Windows Azure Fabric. 2014/01/15 22:44:48 ExpectedState: Started 2014/01/15 22:44:48 ContainerId: fc217d55-31e7-485e-a82f-75b2a90a1a0a 2014/01/15 22:44:48 RoleInstanceId: ba5ce29e7b4d435f8d70ed5b7c471875.utl-0115-s1 2014/01/15 22:44:49 Public cert with thumbprint: D3BCD6F2904D5E4B5E8155ED1E0A698C7B14F007 was retrieved. 2014/01/15 22:46:09 Configured SSH client probing to keep connections alive. 2014/01/15 22:46:09 Windows Azure Linux Agent Version: WALinuxAgent-1.3.2 2014/01/15 22:46:09 Linux Distribution Detected : Ubuntu 2014/01/15 22:46:09 IPv4 address: 100.92.36.21 2014/01/15 22:46:09 MAC address: 00:15:5D:86:BE:4D 2014/01/15 22:46:09 Probing for Windows Azure environment. 2014/01/15 22:46:09 DoDhcpWork: Setting socket.timeout=10, entering recv 2014/01/15 22:46:09 Discovered Windows Azure endpoint: 100.92.36.60 2014/01/15 22:46:09 WARNING:Newer wire protocol version detected. Please consider updating waagent. 2014/01/15 22:46:09 Negotiated wire protocol version: 2011-12-31 2014/01/15 22:46:09 Retrieved GoalState from Windows Azure Fabric. 2014/01/15 22:46:09 ExpectedState: Started 2014/01/15 22:46:09 ContainerId: fc217d55-31e7-485e-a82f-75b2a90a1a0a 2014/01/15 22:46:09 RoleInstanceId: ba5ce29e7b4d435f8d70ed5b7c471875.utl-0115-s1 2014/01/15 22:46:09 Public cert with thumbprint: D3BCD6F2904D5E4B5E8155ED1E0A698C7B14F007 was retrieved. 2014/01/15 22:54:32 Windows Azure Linux Agent Version: WALinuxAgent-1.3.2 2014/01/15 22:54:32 Linux Distribution Detected : Ubuntu 2014/01/15 22:54:32 IPv4 address: 100.92.38.42 2014/01/15 22:54:32 MAC address: 00:15:5D:86:BC:79 2014/01/15 22:54:32 Probing for Windows Azure environment. 2014/01/15 22:54:33 DoDhcpWork: Setting socket.timeout=10, entering recv 2014/01/15 22:54:33 Discovered Windows Azure endpoint: 100.92.38.150 2014/01/15 22:54:33 WARNING:Newer wire protocol version detected. Please consider updating waagent. 2014/01/15 22:54:33 Negotiated wire protocol version: 2011-12-31 2014/01/15 22:54:33 Retrieved GoalState from Windows Azure Fabric. 2014/01/15 22:54:33 ExpectedState: Started 2014/01/15 22:54:33 ContainerId: 6a3ea5a9-6f7c-422f-a026-e6b5eb8f0fe5 2014/01/15 22:54:33 RoleInstanceId: fd9cfa887ac24eeab7efc8e5b48d799a.utl-0115-utl-0115-s1-A1 2014/01/15 22:54:33 Public cert with thumbprint: D3BCD6F2904D5E4B5E8155ED1E0A698C7B14F007 was retrieved. -- 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/1269626 Title: cloud-init Azure Datasource does not detect new instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+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 1269626] Re: cloud-init Azure Datasource does not detect new instance
Okay, I figured it outwe have a race condition. What is happening is that the Windows Azure datasource starts WALinuxAgent. WALinuxAgent normally goes off and fetches a bunch of files. The datasource normally waits for files to show up from WALinuxAgent. In the case of a capture, the files remain there, unless the user removes them. The end result is that by the time WALinuxAgent gets the files, cloud-init has consumed the previous files. -- 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/1269626 Title: cloud-init Azure Datasource does not detect new instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+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 1190986] Re: ERROR Nonce already used
** Changed in: maas Milestone: None = 14.04 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1190986 Title: ERROR Nonce already used To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1190986/+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 1269626] Re: cloud-init Azure Datasource does not detect new instance
** Branch linked: lp:~utlemming/cloud-init/lp1269626 -- 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/1269626 Title: cloud-init Azure Datasource does not detect new instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+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 1268050] Re: Deprovision breaks iDNS registration when using cloud-init
Uploaded Trusty version. However due to Bug #1269626 machines will not provision correclty upon reboot. The fix for Bug #1269626 and this will be SRU'd together. ** Changed in: walinuxagent (Ubuntu Trusty) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1268050 Title: Deprovision breaks iDNS registration when using cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1268050/+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 1268050] Re: Deprovision breaks iDNS registration when using cloud-init
This bug was fixed in the package walinuxagent - 1.3.2-0ubuntu8 --- walinuxagent (1.3.2-0ubuntu8) trusty; urgency=low * debian/patches/idns_dhcp.patch: only change send-hostname in dhcpclient.conf when send-hostname is already in the config (LP: #1268050). -- Ben Howard ben.how...@ubuntu.com Wed, 15 Jan 2014 13:02:30 -0700 ** Changed in: walinuxagent (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1268050 Title: Deprovision breaks iDNS registration when using cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1268050/+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 1269497] Re: Please upstream the AppArmor profiles
This was already on my todo list for LXC 1.0, but thanks for the bug report :) ** Changed in: lxc (Ubuntu) Status: New = Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided = Wishlist ** Changed in: lxc (Ubuntu) Assignee: (unassigned) = Stéphane Graber (stgraber) -- 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/1269497 Title: Please upstream the AppArmor profiles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1269497/+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 1243790] Re: lxc-ubuntu-cloud should use $HOME/.cache if not root
** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1243790 Title: lxc-ubuntu-cloud should use $HOME/.cache if not root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1243790/+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 1258304] Re: lxc-create fails on IPv6 address
** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1258304 Title: lxc-create fails on IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1005951] Re: lxc-fedora template is broken with fedora 17
** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1005951 Title: lxc-fedora template is broken with fedora 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1005951/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1217730] Re: lxc-create help text error
** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1217730 Title: lxc-create help text error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1217730/+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 1204902] Re: Please add symlink access to a guest's root filesystem
I'd say that if someone really wants that, they should use a hook to create the symlink. I don't think we want this behaviour by default however as it tends to be very confusing for users. Known issues (as found when ubuntu touch was similarly abusing this): - Requires root access to read any of the files - Various syscalls will fail on such paths (one such example is that you can't bind-mount a subdir of such a symlink) - Having one of those paths open when the container dies may prevent some resources from getting destroyed, leading to crashes. ** Changed in: lxc (Ubuntu) Status: Confirmed = Won't Fix -- 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/1204902 Title: Please add symlink access to a guest's root filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1204902/+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 1204903] Re: lxc-info's output should be more easily machine-readable
** Changed in: lxc (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1204903 Title: lxc-info's output should be more easily machine-readable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1204903/+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 1267242] Re: Running lxc-ls as non-root should provide a nicer error message
lxc-ls now shows user containers when run as non-root. ** Changed in: lxc (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1267242 Title: Running lxc-ls as non-root should provide a nicer error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1267242/+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 1224672] Re: lxc-destroy does not remove symlinks in /etc/lxc/auto/
Newer LXC no longer uses /etc/lxc/auto ** Changed in: lxc (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1224672 Title: lxc-destroy does not remove symlinks in /etc/lxc/auto/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1224672/+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 1261338] Re: lxc-stop and even lxc-stop -k can hang
I vaguely remember discussing this on IRC. IIRC the case was something in the container getting stuck in D state because of a kernel bug. In such case, the container couldn't be killed as anything attempting to do so would get stuck too. Anyway, this is pretty unfortunate but it's a kernel bug and there's nothing LXC can do to kill an unkillable process so I think our current behaviour is fine and the kernel is what should get fixed. ** Changed in: lxc (Ubuntu) Status: Incomplete = 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/1261338 Title: lxc-stop and even lxc-stop -k can hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+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 1184932] Re: lxc-halt --name container shuts down host [12.04 3.8 kernel]
We dropped lxc-halt a while back ** Changed in: lxc (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1184932 Title: lxc-halt --name container shuts down host [12.04 3.8 kernel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1184932/+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 1196295] Re: lxc-start enters uninterruptible sleep
Marking as invalid for LXC since this is a kernel bug. ** Changed in: lxc (Ubuntu) Status: Confirmed = 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/1196295 Title: lxc-start enters uninterruptible sleep To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1196295/+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 1166841] Re: lxc-create fails if LANG is not valid
Sent a patch upstream to ignore the failure. ** Changed in: lxc (Ubuntu) Status: Triaged = Fix Committed -- 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/1166841 Title: lxc-create fails if LANG is not valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1166841/+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 1269674] [NEW] package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 126
Public bug reported: Does not upgrade samba4, error update. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-45.68~precise1-generic 3.5.7.26 Uname: Linux 3.5.0-45-generic i686 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: cont4-contl: Install cont4-gestl: Install samba4: Configure cont4-contl: Configure cont4-gestl: Configure Architecture: i386 Date: Wed Jan 15 21:30:32 2014 DuplicateSignature: package:samba4:4.0.0~alpha18.dfsg1-4ubuntu2:el subproceso instalado el script post-installation devolvió el código de salida de error 126 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 126 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True SourcePackage: samba4 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 126 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba4 in Ubuntu. https://bugs.launchpad.net/bugs/1269674 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1269674/+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 1159818] Re: Allow architecture armhf with template ubuntu-cloud when running on ARM
root@delmak:~# lxc-create -t ubuntu-cloud -n p1 -- -r trusty -s daily mapped_uid is .-1. ubuntu-cloudimg-query is /usr/bin/ubuntu-cloudimg-query wget is /usr/bin/wget --2014-01-16 03:32:09-- https://cloud-images.ubuntu.com/server/trusty/20140115/trusty-server-cloudimg-armhf-root.tar.gz Resolving cloud-images.ubuntu.com (cloud-images.ubuntu.com)... 91.189.88.141 Connecting to cloud-images.ubuntu.com (cloud-images.ubuntu.com)|91.189.88.141|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://cloud-images.ubuntu.com/trusty/20140115/trusty-server-cloudimg-armhf-root.tar.gz [following] --2014-01-16 03:32:09-- https://cloud-images.ubuntu.com/trusty/20140115/trusty-server-cloudimg-armhf-root.tar.gz Reusing existing connection to cloud-images.ubuntu.com:443. HTTP request sent, awaiting response... 200 OK Length: 169767486 (162M) [application/x-gzip] Saving to: ‘trusty-server-cloudimg-armhf-root.tar.gz’ 100%[] 169,767,486 1.06MB/s in 3m 17s 2014-01-16 03:35:26 (842 KB/s) - ‘trusty-server-cloudimg-armhf- root.tar.gz’ saved [169767486/169767486] Extracting container rootfs perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = en_US.UTF-8, LC_ALL = en_US.UTF-8, LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory Current default time zone: 'Etc/UTC' Local time is now: Thu Jan 16 03:36:06 UTC 2014. Universal Time is now: Thu Jan 16 03:36:06 UTC 2014. Container p1 created. ** Changed in: lxc (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1159818 Title: Allow architecture armhf with template ubuntu-cloud when running on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1159818/+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 1167394] Re: segfaults with php-fpm and current php5-memcached
[Expired for php5 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: php5 (Ubuntu) Status: Incomplete = Expired -- 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/1167394 Title: segfaults with php-fpm and current php5-memcached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1167394/+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
