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
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 c
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:
ht
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: unterminat
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
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
Date: Sun Nov 3 00:15:05 20
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
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:
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
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-sens
** 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 d
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: iscsitarg
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
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 commiss
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 t
** 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)
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 b
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.
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
> Ok i will test in next days
> Am 09.01.2014 17:53 schrieb "Phillip Susi" :
>
> The backport to precise is still waiting for someone to test
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
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 thi
** 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
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/consol
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: INPROGRE
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:/
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
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
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 a
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 sa
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.
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 affect
** 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"
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 ()
Jan 15 20:09:31 utl-0115-lp1268050 [CLOUDINIT] cc_power_state_change.py[DEBUG]:
no pow
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-
** 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.lau
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
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 clou
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 @@
-
-
-
+
+
+
-
-
+
+
>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
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 rem
** 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:
h
** 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 ma
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
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
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
** 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 ro
** 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 notifi
** 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 m
** 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 notification
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
** 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
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:
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
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 an
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 contai
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
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-creat
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
AptOrder
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
[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/bu
Serge: I've got a patch that fixes the problem. I've uploaded a test
build along with the patch to:
http://people.canonical.com/~sforshee/lp1263738/linux-3.13.0-3.18~lp1263738v201401152110/
I still want to verify that it's impossible to steal a tty from a
process in a parent namespace, but if tha
61 matches
Mail list logo
