[Bug 613022] Re: ssh daemon hangs after publickey packet sent
** Changed in: openssh (Ubuntu) Status: New = Confirmed -- 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/613022 Title: ssh daemon hangs after publickey packet sent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/613022/+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 628577] Re: connection fails: ssh_exchange_identification
marking incomplete. without more information, there is no real way to debug this. ** Changed in: openssh (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/628577 Title: connection fails: ssh_exchange_identification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/628577/+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 904480] Re: change default networking to virtio in Ubuntu packaging
On Thu, 15 Dec 2011, Dave Walker wrote: When people toll Windows AMI's, do they tend to include the drivers for virtio? I honestly don't know much about windows. I know that virtio drivers are available for windows, and I actually believe you can get them signed by Canonical. google is failing me now, though. I think temporary pain in getting virtio drivers for windows is more than overcome by not having to make this change later and breaking existing amis. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/904480 Title: change default networking to virtio in Ubuntu packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/904480/+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 905419] Re: cloud-init messages going to syslog, not cloud-init.log
** Changed in: cloud-init (Ubuntu) Importance: Undecided = Medium ** Changed in: cloud-init (Ubuntu) Status: New = Confirmed -- 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/905419 Title: cloud-init messages going to syslog, not cloud-init.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/905419/+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 905419] [NEW] cloud-init messages going to syslog, not cloud-init.log
Public bug reported: on boot of a precise image, I did not see messages in /var/log/cloud- init.log as expected. I noticed that some of them are in /var/log/syslog: Dec 16 16:41:30 server-3393 d-init-cfg[INFO]: cloud-init-cfg ['all', 'config'] Dec 16 16:41:30 server-3393 it__.py[DEBUG]: handling mounts with freq=None and args=[] Dec 16 16:41:30 server-3393 SourceEc2.py[DEBUG]: unable to convert swap to a device Dec 16 16:41:30 server-3393 kernel: [ 83.058563] kjournald starting. Commit interval 5 seconds Dec 16 16:41:30 server-3393 it__.py[DEBUG]: handling ssh-import-id with freq=None and args=[] Dec 16 16:41:30 server-3393 sh_import_id.py[DEBUG]: importing ssh ids. cmd = ['sudo', '-Hu', 'ubuntu', 'ssh-import-id', 'smoser'] I'm not sure where the beginning of those log statements are going. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cloud-init 0.6.2-0ubuntu1 ProcVersionSignature: User Name 3.2.0-4.10-virtual 3.2.0-rc5 Uname: Linux 3.2.0-4-virtual x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Fri Dec 16 17:29:28 2011 Ec2AMI: ami-0102 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug ec2-images precise -- 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/905419 Title: cloud-init messages going to syslog, not cloud-init.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/905419/+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 905419] Re: cloud-init messages going to syslog, not cloud-init.log
It seems this is possibly rsyslog or python logging related, because cloud-init did not change between oneiric and precise,. In oneiric, it works: Dec 16 17:36:04 server-3395 [CLOUDINIT] __init__.py[DEBUG]: handling final-message with freq=None and args=[] Dec 16 21:11:30 server-3395 [CLOUDINIT] cloud-init-cfg[INFO]: cloud-init-cfg ['apt-update-upgrade', 'always'] Dec 16 21:11:30 server-3395 [CLOUDINIT] __init__.py[DEBUG]: handling apt-update-upgrade with freq=always and args=[] That final message in /var/log/cloud-init.log was generated when I just now (4 hours after booting) ran: sudo cloud-init-cfg apt-update-upgrade always -- 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/905419 Title: cloud-init messages going to syslog, not cloud-init.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/905419/+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 905419] Re: cloud-init messages going to syslog, not cloud-init.log
You can compare the output above, with what i found in /var/log/syslog after running he same on precise: Dec 16 21:14:02 server-3393 d-init-cfg[INFO]: cloud-init-cfg ['apt-update-upgrade', 'always'] Dec 16 21:14:02 server-3393 it__.py[DEBUG]: handling apt-update-upgrade with freq=always and args=[] Dec 16 21:14:02 server-3393 pt_update_upgrade.py[DEBUG]: selected mirror at: http://ubuntu-mirror.novalocal/ubuntu It seems like data is being lost for a message. -- 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/905419 Title: cloud-init messages going to syslog, not cloud-init.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/905419/+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 905419] Re: cloud-init messages going to syslog, not cloud-init.log
I'm moving this to package rsyslog, I've verified that this is a regression
caused by using rsyslog from precise (5.8.6-1ubuntu3).
The issue is fixed and demonstrable by:
$
url=https://launchpad.net/ubuntu/+archive/primary/+files/rsyslog_5.8.1-1ubuntu2_amd64.deb;
$ wget $url -O ${url##*/}
$ sudo dpkg -i ${url##*/}
$ sudo cloud-init start
After the above, a message from 'cloud-init start' will be in /var/log
/cloud-init.log. Running that otherwise would put the mangled message
in /var/log/syslog.
** Description changed:
on boot of a precise image, I did not see messages in /var/log/cloud-
init.log as expected.
I noticed that some of them are in /var/log/syslog:
Dec 16 16:41:30 server-3393 d-init-cfg[INFO]: cloud-init-cfg ['all', 'config']
Dec 16 16:41:30 server-3393 it__.py[DEBUG]: handling mounts with freq=None
and args=[]
Dec 16 16:41:30 server-3393 SourceEc2.py[DEBUG]: unable to convert swap to a
device
Dec 16 16:41:30 server-3393 kernel: [ 83.058563] kjournald starting.
Commit interval 5 seconds
Dec 16 16:41:30 server-3393 it__.py[DEBUG]: handling ssh-import-id with
freq=None and args=[]
Dec 16 16:41:30 server-3393 sh_import_id.py[DEBUG]: importing ssh ids. cmd =
['sudo', '-Hu', 'ubuntu', 'ssh-import-id', 'smoser']
+ I'm not sure where the beginning of those log statements are going.
- I'm not sure where the beginning of those log statements are going.
+ cloud-init uses python logging, and places the following content in
/etc/rsyslog.d/21-cloudinit.conf:
+ # Log cloudinit generated log messages to file
+ :syslogtag, isequal, [CLOUDINIT] /var/log/cloud-init.log
+
+ # comment out the following line to allow CLOUDINIT messages through.
+ # Doing so means you'll also get CLOUDINIT messages in /var/log/syslog
+ ~
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: cloud-init 0.6.2-0ubuntu1
ProcVersionSignature: User Name 3.2.0-4.10-virtual 3.2.0-rc5
Uname: Linux 3.2.0-4-virtual x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Fri Dec 16 17:29:28 2011
Ec2AMI: ami-0102
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
- PATH=(custom, user)
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ PATH=(custom, user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
** Package changed: cloud-init (Ubuntu) = rsyslog (Ubuntu)
** Tags added: regression-release
--
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/905419
Title:
cloud-init messages going to syslog, not cloud-init.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/905419/+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 894279] Re: cloud-init fails to fetch metadata with OpenStack
@Juerg, Could you test out the cloud-init at trunk right now and see if it fixes your problem? The commit at http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/488 hopefully has a readable description of hte change. To build a upstream cloud-init, you can just run: ./tools/bddeb ** Changed in: cloud-init Importance: Undecided = High ** Changed in: cloud-init Status: New = Fix Committed ** Changed in: cloud-init Assignee: (unassigned) = Scott Moser (smoser) -- 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/894279 Title: cloud-init fails to fetch metadata with OpenStack To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/894279/+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 903993] Re: Don't hang waiting for input from commands
** Changed in: cloud-init Importance: Undecided = Medium ** Changed in: cloud-init Status: New = In Progress ** Changed in: cloud-init Assignee: (unassigned) = Scott Moser (smoser) -- 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/903993 Title: Don't hang waiting for input from commands To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/903993/+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 903993] Re: Don't hang waiting for input from commands
fix-commited in upstream cloud-init at revision 490. -- 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/903993 Title: Don't hang waiting for input from commands To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/903993/+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 893786] Re: mount option can`t set permissions
What sort of syntax would you suggest for cloud-config to set permissions on a mount? I'm expecting that in your example you just want to have ubuntu:ubuntu as the ownership so that the default user could use it. ** Changed in: cloud-init Importance: Undecided = Wishlist ** Changed in: cloud-init Status: New = Triaged ** Changed in: cloud-init (Ubuntu) Status: New = Triaged -- 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/893786 Title: mount option can`t set permissions To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/893786/+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 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
** Changed in: cloud-init (Ubuntu) Importance: Undecided = Medium ** Changed in: cloud-init Importance: Undecided = Medium -- 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/890501 Title: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/890501/+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 871966] Re: FQDN written to /etc/hosts causes problems for clustering systems
** Changed in: cloud-init Status: New = Triaged ** Changed in: cloud-init Importance: Undecided = Medium ** Changed in: cassandra (juju Charms Collection) Importance: Undecided = Medium -- 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/871966 Title: FQDN written to /etc/hosts causes problems for clustering systems To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/871966/+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 903993] Re: Don't hang waiting for input from commands
** Changed in: cloud-init Status: In Progress = Fix Committed -- 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/903993 Title: Don't hang waiting for input from commands To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/903993/+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 893786] Re: mount option can`t set permissions
On Tue, 20 Dec 2011, Björn Dieding wrote: Yes something like this. - [ ephemeral0, /mnt/ephemeral, auto, defaults, ubuntu:ubuntu, 0755 ] Hm... i suppose we could add a field there, but it wouldn't be ideal. I like the fact that the fields represent exactly what is in /etc/fstab. But any other solution would require mapping the entry to directory. -- 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/893786 Title: mount option can`t set permissions To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/893786/+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 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
This is fix-commited in cloud-init in revision 491 (http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/491). See the commit message there for more information. ** Changed in: cloud-init Status: New = Fix Committed ** Changed in: cloud-init Assignee: (unassigned) = Scott Moser (smoser) -- 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/890501 Title: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/890501/+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 871966] Re: FQDN written to /etc/hosts causes problems for clustering systems
This is fix-commited in cloud-init in revision 491 (http://bazaar.launchpad.net/~cloud-init-dev/cloud- init/trunk/revision/491). See the commit message there for more information. ** Changed in: cloud-init (Ubuntu Precise) Status: Confirmed = Fix Committed -- 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/871966 Title: FQDN written to /etc/hosts causes problems for clustering systems To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/871966/+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 871966] Re: FQDN written to /etc/hosts causes problems for clustering systems
This is fix-commited in cloud-init in revision 491 (http://bazaar.launchpad.net/~cloud-init-dev/cloud- init/trunk/revision/491). See the commit message there for more information. ** Changed in: cloud-init (Ubuntu Precise) Status: Fix Committed = Triaged ** Changed in: cloud-init Status: Triaged = Fix Committed ** Changed in: cloud-init Assignee: (unassigned) = Scott Moser (smoser) ** Changed in: cloud-init (Ubuntu Precise) Assignee: (unassigned) = Scott Moser (smoser) -- 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/871966 Title: FQDN written to /etc/hosts causes problems for clustering systems To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/871966/+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 893400] Re: cloud-init: Output public ssh host key (for known_hosts)
** Changed in: cloud-init Status: Triaged = In Progress ** Changed in: cloud-init Assignee: (unassigned) = Scott Moser (smoser) -- 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/893400 Title: cloud-init: Output public ssh host key (for known_hosts) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/893400/+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 893400] Re: cloud-init: Output public ssh host key (for known_hosts)
fix-committed in cloud-init trunk at http://bazaar.launchpad.net/~cloud- init-dev/cloud-init/trunk/revision/493 . ** Changed in: cloud-init Status: In Progress = Fix Committed -- 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/893400 Title: cloud-init: Output public ssh host key (for known_hosts) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/893400/+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
[Merge] lp:~smoser/ubuntu/precise/rsyslog/lp905419 into lp:ubuntu/rsyslog
Scott Moser has proposed merging lp:~smoser/ubuntu/precise/rsyslog/lp905419
into lp:ubuntu/rsyslog.
Requested reviews:
Ubuntu Server Team (ubuntu-server)
Related bugs:
Bug #905419 in rsyslog (Ubuntu): messages to rsyslog without timestamp lose
16 chars
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/905419
For more details, see:
https://code.launchpad.net/~smoser/ubuntu/precise/rsyslog/lp905419/+merge/86429
--
https://code.launchpad.net/~smoser/ubuntu/precise/rsyslog/lp905419/+merge/86429
Your team Ubuntu Server Team is requested to review the proposed merge of
lp:~smoser/ubuntu/precise/rsyslog/lp905419 into lp:ubuntu/rsyslog.
=== modified file '.pc/applied-patches'
--- .pc/applied-patches 2011-11-07 13:54:56 +
+++ .pc/applied-patches 2011-12-20 16:43:34 +
@@ -1,1 +1,2 @@
01-dont_create_db.patch
+100-imuxsock-allow-missing-date.patch
=== modified file 'debian/changelog'
--- debian/changelog 2011-12-02 17:39:39 +
+++ debian/changelog 2011-12-20 16:43:34 +
@@ -1,3 +1,11 @@
+rsyslog (5.8.6-1ubuntu4) UNRELEASED; urgency=low
+
+ * debian/patches/100-imuxsock-allow-missing-date.patch
+fix bug in imuxsock that truncated messages if they did not
+contain a date field (LP: #905419).
+
+ -- Scott Moser smo...@ubuntu.com Tue, 20 Dec 2011 11:07:16 -0500
+
rsyslog (5.8.6-1ubuntu3) precise; urgency=low
* No-change rebuild to drop spurious libsfgcc1 dependency on armhf.
=== added file 'debian/patches/100-imuxsock-allow-missing-date.patch'
--- debian/patches/100-imuxsock-allow-missing-date.patch 1970-01-01 00:00:00 +
+++ debian/patches/100-imuxsock-allow-missing-date.patch 2011-12-20 16:43:34 +
@@ -0,0 +1,34 @@
+From: Rainer Gerhards rgerha...@adiscon.com
+Date: Tue, 20 Dec 2011 15:39:39 + (+0100)
+Subject: bugfix: imuxsock did truncate part of received message if it did not contain a proper...
+X-Git-Url: http://git.adiscon.com/?p=rsyslog.git;a=commitdiff_plain;h=f112b51b8d6c358b87ac608112d393adb047ea0f
+
+bugfix: imuxsock did truncate part of received message if it did not contain a proper date.
+
+The truncation occured because we removed that part of the messages
+that was expected to be the date.
+closes: http://bugzilla.adiscon.com/show_bug.cgi?id=295
+
+Origin: upstream, http://git.adiscon.com/?p=rsyslog.git;a=commitdiff_plain;h=f112b51b8d6c358b87ac608112d393adb047ea0f
+Bug: http://bugzilla.adiscon.com/show_bug.cgi?id=295
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/905419
+---
+
+diff --git a/plugins/imuxsock/imuxsock.c b/plugins/imuxsock/imuxsock.c
+index 2697c48..feddb20 100644
+--- a/plugins/imuxsock/imuxsock.c
b/plugins/imuxsock/imuxsock.c
+@@ -565,8 +565,11 @@ SubmitMsg(uchar *pRcv, int lenRcv, lstn_t *pLstn, struct ucred *cred)
+ parse++; lenMsg--; /* '' */
+
+ if((pLstn-flags IGNDATE)) {
+- parse += 16; /* just skip timestamp */
+- lenMsg -= 16;
++ /* in this case, we still need to find out if we have a valid
++ * datestamp or not .. and advance the parse pointer accordingly.
++ */
++ struct syslogTime dummy;
++ datetime.ParseTIMESTAMP3164(dummy, parse, lenMsg);
+ } else {
+ if(datetime.ParseTIMESTAMP3164((pMsg-tTIMESTAMP), parse, lenMsg) != RS_RET_OK) {
+ DBGPRINTF(we have a problem, invalid timestamp in msg!\n);
=== modified file 'debian/patches/series'
--- debian/patches/series 2011-11-07 13:54:56 +
+++ debian/patches/series 2011-12-20 16:43:34 +
@@ -1,2 +1,4 @@
# Debian patches for rsyslog
01-dont_create_db.patch
+# Ubuntu patches for rsyslog
+100-imuxsock-allow-missing-date.patch
=== modified file 'plugins/imuxsock/imuxsock.c'
--- plugins/imuxsock/imuxsock.c 2011-11-02 23:31:41 +
+++ plugins/imuxsock/imuxsock.c 2011-12-20 16:43:34 +
@@ -565,8 +565,11 @@
parse++; lenMsg--; /* '' */
if((pLstn-flags IGNDATE)) {
- parse += 16; /* just skip timestamp */
- lenMsg -= 16;
+ /* in this case, we still need to find out if we have a valid
+ * datestamp or not .. and advance the parse pointer accordingly.
+ */
+ struct syslogTime dummy;
+ datetime.ParseTIMESTAMP3164(dummy, parse, lenMsg);
} else {
if(datetime.ParseTIMESTAMP3164((pMsg-tTIMESTAMP), parse, lenMsg) != RS_RET_OK) {
DBGPRINTF(we have a problem, invalid timestamp in msg!\n);
--
Ubuntu-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 857366] Re: support configuring landscape-client in cloud-config format
** Changed in: cloud-init Status: Triaged = In Progress ** Changed in: cloud-init Assignee: (unassigned) = Scott Moser (smoser) -- 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/857366 Title: support configuring landscape-client in cloud-config format To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/857366/+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 857366] Re: support configuring landscape-client in cloud-config format
** Branch linked: lp:~smoser/cloud-init/landscape-client.lp857366 -- 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/857366 Title: support configuring landscape-client in cloud-config format To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/857366/+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 857366] Re: support configuring landscape-client in cloud-config format
fix-commited in trunk rev 496 http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/496 ** Changed in: cloud-init Status: In Progress = Fix Committed -- 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/857366 Title: support configuring landscape-client in cloud-config format To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/857366/+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 900972] Re: lxc instance console output spewed to stdout
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: I ran an instance of oneiric and ran LIBVIRT_TYPE=lxc for devstack. - When I ran an instance, the console output of the instance came to the - devstack screen's 0th window. + When I ran an instance, of http://smoser.brickies.net/ubuntu/ttylinux- + uec/ttylinux-uec-amd64-11.2_2.6.35-15_1.tar.gz , the console output of + the instance came to the devstack screen's 0th window. I'm guessing that the ttylinux image is doing something less than ideal, but it should not really have access to that resource. - I'm attaching the output from screen 0' window as I saw it. Note the messages from the lxc guest. -- 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/900972 Title: lxc instance console output spewed to stdout To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/900972/+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 524020] Re: karmic uec builds fail to publish due to 2 installed -ec2 kernels
I'm marking this Wont fix. You could fix it, but really the issue was with karmic's archive. and no need to work around that. ** Changed in: vm-builder (Ubuntu) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/524020 Title: karmic uec builds fail to publish due to 2 installed -ec2 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/524020/+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 871966] Re: FQDN written to /etc/hosts causes problems for clustering systems
Jason, I would actually like to not pull the fix back to oneiric. As doing so would break people using oneiric who were expecting the behavior that is present there now. At very least we have to think seriously about it and come up with a list of what types of users would be affected. Do you have any thoughts? -- 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/871966 Title: FQDN written to /etc/hosts causes problems for clustering systems To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/871966/+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 912355] [NEW] euca-allocate-address is not acepting any parameters
On Thu, 5 Jan 2012, Nicolas Valcarcel wrote: Public bug reported: euca-allocate-address is ignoring the address passed to it and instead using the next ip not allocated: What made you think that it was supposed to take a parameter? ec2-allocate-address does not take parameters. Maybe some eucalyptus specific code did? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/912355 Title: euca-allocate-address is not acepting any parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/euca2ools/+bug/912355/+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 912066] Re: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present.
Kiall, could you collect the ec2 metadata from inside such an instance? python -c 'import boto.utils, pprint; pprint.pprint(boto.utils.get_instance_metadata())' Basically, i suspect that the metadata is stating that swap is at /dev/vdc, so cloud-init is trusting it. if that is the case, we either have to : a.) go searching for swap b.) fix nova metadata service and 'b' seems like the right fix, as the MD is clearly wrong. -- 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/912066 Title: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/912066/+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 912355] Re: euca-allocate-address is not acepting any parameters
** Also affects: euca2ools Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/912355 Title: euca-allocate-address is not acepting any parameters To manage notifications about this bug go to: https://bugs.launchpad.net/euca2ools/+bug/912355/+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 912355] Re: euca-allocate-address is not acepting any parameters
@Mitch, or Garrett Do you have a thoughts on this? I certainly dont see anything in current euca2ools that would take an address for euca-allocate-address. A quick look doesn't show back at even euca2ools 1.3.1 didn't show anything like this. It seems to me that the docs.openstack.org link above is just plain wrong. but maybe i'm missing something. http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/ApiReference-query-AllocateAddress.html doesn't show anything of the sort. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/912355 Title: euca-allocate-address is not acepting any parameters To manage notifications about this bug go to: https://bugs.launchpad.net/euca2ools/+bug/912355/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-p-cloudimages-cloudinit] Improvements to Cloud-init or Cloud Images
Blueprint changed by Scott Moser: Whiteboard changed: Etherpad: edit: http://pad.ubuntu.com/uds-p-servercloud-p-cloudimages-cloudinit time slider: http://pad.ubuntu.com/ep/pad/view/uds-p-servercloud-p-cloudimages-cloudinit/latest Work Items: Implement public glance server: TODO Canonical IS ticket for public glance server: TODO Populate glance server on build finish: TODO Provide clean /query2 data pointing to .img files: TODO hand off glance server to canonical IS: TODO [smoser] make ec2-publishing-scripts publish instance-store concurrently: DONE [smoser] make ec2-publishing-scripts publish ebs concurrently: DONE [smoser] make ec2-publishing-scripts describe-images much less (speed): DONE [smoser] add serial number to daily HEADER.html output: DONE [smoser] trouble shoot publish parallel fallout as it comes in: DONE [smoser] re-implement EBS publishing to not require ssh or elastic IP: TODO sync/merge with upstream cdimage scripts and nectarine: TODO - cloud-init fix /etc/hosts editing (bug 871966, bug 890501): TODO + cloud-init fix /etc/hosts editing (bug 871966, bug 890501): DONE cloud-init upstream add unit test: TODO cloud-init support userdata, metadata from configdrive (bug 857378): TODO cloud-init support network config via configdrive: TODO - cloud-init support cloud-local mirrors via dns naming convention: TODO + cloud-init support cloud-local mirrors via dns naming convention: DONE cloud-init support cloud-local proxy via dns naming convention: TODO better documentation rebundling via user-data and kvm: TODO follow up with aligouri on definitive qcow format link for OVF: DONE -- Improvements to Cloud-init or Cloud Images https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloudimages-cloudinit -- Ubuntu-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 914679] [NEW] /run is not setup as tmpfs
Public bug reported: The place I saw this bug is the following failure, but serge asked me to open this bug against libguestfs. Inside a container created by juju, I see: root@ubuntu-jstack-nova-compute-0:~# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up open-iscsi (2.0.871-0ubuntu9) ... update-rc.d: warning: open-iscsi stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 6) * Starting iSCSI initiator service iscsid ...fail! ln: target `/run/sendsigs.omit.d/' is not a directory: No such file or directory * Setting up iSCSI targets ...done. invoke-rc.d: initscript open-iscsi, action start failed. dpkg: error processing open-iscsi (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of nova-compute: nova-compute depends on open-iscsi; however: Package open-iscsi is not configured yet. dpkg: error processing nova-compute (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of nova-compute-kvm: nova-compute-kvm depends on nova-compute (= 2012.1~e2-0ubuntu2); however: Package nova-compute is not configured yet. dpkg: error processing nova-compute-kvm (--configure): dependency problems - leaving unconfigured 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. Errors were encountered while processing: open-iscsi nova-compute nova-compute-kvm ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxcguest 0.7.5-3ubuntu4 ProcVersionSignature: User Name 3.2.0-8.14-virtual 3.2.0 Uname: Linux 3.2.0-8-virtual x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Wed Jan 11 10:24:02 2012 Dependencies: Ec2AMI: ami-0129 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- 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/914679 Title: /run is not setup as tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/914679/+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 915282] [NEW] cloud-init does not select ec2 mirrors
Public bug reported: cloud-init in precise is not selecting the ec2 mirrors. this is a regression in the latest upload. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cloud-init 0.6.3~bzr497-0ubuntu1 [modified: usr/share/pyshared/cloudinit/CloudConfig/cc_apt_update_upgrade.py] ProcVersionSignature: User Name 3.2.0-8.15-virtual 3.2.0 Uname: Linux 3.2.0-8-virtual x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 12 12:15:12 2012 Ec2AMI: ami-5feb3c36 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-825ea7eb Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- 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/915282 Title: cloud-init does not select ec2 mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/915282/+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 915282] Re: cloud-init does not select ec2 mirrors
-- 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/915282 Title: cloud-init does not select ec2 mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/915282/+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 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
I believe we talked once about doing the CNAME solution, and the decision was made not to implement it. The reason was (from memory) that if we did, all requests would then hit external mirrors, and subsequently we would have to open up all traffic to the ec2 mirrors that canonical IS is running. The decision was not to do that. So, the other solution here is: a.) SRU the fix in cloud-init to lucid b.) wait until the s3 backed mirrors are live B is expected inside of 30 days, and the SRU takes at least 2 weeks to get into the archive. We expect that s3 backed mirrors will be open to the world, so this will not be a problem anymore. -- 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/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+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 737882] Re: cloud-init bails when any mimetype is non text
** Changed in: cloud-init (Ubuntu) Status: Confirmed = Fix Released -- 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/737882 Title: cloud-init bails when any mimetype is non text To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/737882/+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 766242] Re: lp:ubuntu/cloud-init is not buildable by bzr-builder
generally, i think that bzr-builder should be better, and allow for no
.pc directory but applied patches.
However, cloud-init's ubuntu trunk is now an upstream snapshot, so:
$ cat cloud-init.recipe EOF
# bzr-builder format 0.4 deb-version {debupstream}-0ubuntu0+{revno}
lp:ubuntu/cloud-init
EOF
$ bzr dailydeb cloud-init.recipe working-dir
That worked for me today on precise, with, building '0.6.3~bzr502-0ubuntu1'
bzr-builder 0.7.2-0ubuntu1
using 'format 0.3' works also (so probably older bzr-builders would
work).
** Changed in: cloud-init (Ubuntu)
Status: Confirmed = Fix Released
--
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/766242
Title:
lp:ubuntu/cloud-init is not buildable by bzr-builder
To manage notifications about this bug go to:
https://bugs.launchpad.net/bzr-builder/+bug/766242/+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 665235] Re: grub-legacy-ec2: attaching a volume to maverick instance may boot off it
** Changed in: cloud-init (Ubuntu) Status: Confirmed = Won't Fix -- 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/665235 Title: grub-legacy-ec2: attaching a volume to maverick instance may boot off it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-on-ec2/+bug/665235/+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 871297] Re: uncloud-init updates.tar doesn't work
** Changed in: cloud-init (Ubuntu) Status: Triaged = Fix Released -- 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/871297 Title: uncloud-init updates.tar doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/871297/+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 613022] Re: ssh daemon hangs after publickey packet sent
marking invalid on cloud-init, definitely the bug was not/is-not here. ** Changed in: cloud-init (Ubuntu) Status: Confirmed = Invalid -- 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/613022 Title: ssh daemon hangs after publickey packet sent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/613022/+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 664529] Re: cloud-init hangs with url error 'Network is unreachable'
i'd not commented on this since maverick, and i'm not fixing this very rare occurance there. I think its most likely a race. ** Changed in: cloud-init (Ubuntu) Status: Confirmed = Won't Fix -- 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/664529 Title: cloud-init hangs with url error 'Network is unreachable' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/664529/+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 917471] Re: Please upgrade to the latest upstream bug fix release for precise
** Changed in: bacula (Ubuntu) Assignee: (unassigned) = Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/917471 Title: Please upgrade to the latest upstream bug fix release for precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/917471/+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 918327] Re: lxc-start exits success on failure when non-root
-- 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/918327 Title: lxc-start exits success on failure when non-root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918327/+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 918327] [NEW] lxc-start exits success on failure when non-root
Public bug reported: $ sudo lxc-create -t ubuntu -n lv1 $ lxc-start -n lv1 -d $ echo $? 0 $ lxc-ls lv1 $ lxc-list RUNNING STOPPED lv1 I would have expected an error message when trying to start a container that I did not have acl to start. instead, lxc-start exited success (0) and gave no output. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu5 ProcVersionSignature: User Name 3.2.0-8.15-virtual 3.2.0 Uname: Linux 3.2.0-8-virtual x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Wed Jan 18 18:11:17 2012 Ec2AMI: ami-012b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- 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/918327 Title: lxc-start exits success on failure when non-root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918327/+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 918327] Re: lxc-start exits success on failure when non-root
Another (likely related) issue, after using sudo to start the container, observe: $ lxc-ls lv1 $ sudo lxc-start -n lv1 -d $ lxc-ls lv1 /usr/bin/lxc-ls: line 35: cd: /sys/fs/cgroup/cpuset///lxc: Permission denied ls: cannot access lv1: No such file or directory $ sudo lxc-ls lv1 lv1 $ sudo lxc-list RUNNING lv1 STOPPED So, as it is now after starting the container 'sudo lxxc-ls' shows 2 containers, but 'lxc-ls' (without sudo) shows annoying messages. -- 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/918327 Title: lxc-start exits success on failure when non-root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918327/+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 898373] Re: fsck.ext3: Device or resource busy while trying to open /dev/xvda2
Seen in jenkins daily runs in build at [1]. Specifically, see console log of instance at [2] -- [1] https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/job/precise-server-ec2-daily/ARCH=i386,REGION=eu-west-1,STORAGE=instance-store,label=ubuntu-server-ec2-testing/45/ [2] https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/job/precise-server-ec2-daily/ARCH=i386,REGION=eu-west-1,STORAGE=instance-store,label=ubuntu-server-ec2-testing/45/artifact/None/i386/m1.small/instance-store/i-929cf6db/uec2-20120119-0340-74e55fac26b44d-terminated.console.txt -- 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/898373 Title: fsck.ext3: Device or resource busy while trying to open /dev/xvda2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/898373/+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 898373] Re: fsck.ext3: Device or resource busy while trying to open /dev/xvda2
after looking at the console pointed at in comment 3, I thought i might be able to trigger this by issuing 'reboot-instances' on a running node. I was not successful in doing so. In a instance of: eu-west-1 ami-738fb007 ubuntu-precise-daily-i386-server-20120119 I issued reboot via 'euca-reboot-instances' 10 times and colllected log output (the low number is really because it takes 5m to get a console output). None of these resulted in the fsck issue. -- 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/898373 Title: fsck.ext3: Device or resource busy while trying to open /dev/xvda2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/898373/+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 898373] Re: fsck.ext3: Device or resource busy while trying to open /dev/xvda2
after doing this, i caught a fsck device busy error: args=--region=eu-west-1 i-087e0b41' for((i=12;i50;i++)); do echo $(date): i=$i; euca-reboot-instances $args sleep 1m euca-get-console-output $args /tmp/console.hard-reboot$i; done the 37th boot (attaching) showed this error. ** Attachment added: 2 kernel boot consoles, one showing failure https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/898373/+attachment/2683001/+files/console.hard-reboot37 -- 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/898373 Title: fsck.ext3: Device or resource busy while trying to open /dev/xvda2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/898373/+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 918946] [NEW] cannot run libvirt in an 'lxc create -t ubuntu' container
Public bug reported: if you try to start a qemu/kvm guest from inside a container crated by lxc create -t ubuntu, it will fail with something like: error: Failed to start domain my.img error: unable to allow device /dev/full: Operation not permitted $ lxc create -t ubuntu -n lv1 $ lxc-console -n lv1 # login here % apt-get install qemu-kvm % apt-get install dbus # bug 918343 % apt-get install libvirt-bin % qemu-img create -f qcow2 disk.img 1G % virsh define libvirt.xml % virsh start mytest from a working qemu guest, I see: # cat /sys/fs/cgroup/devices/libvirt/qemu/myname/devices.list c 136:* rw c 1:3 rw c 1:7 rw c 1:5 rw c 1:8 rw c 1:9 rw c 5:2 rw c 254:0 rw So I think we need to add access to that list of devices. (haven't testd this all the way yet). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu5 ProcVersionSignature: User Name 3.2.0-8.15-virtual 3.2.0 Uname: Linux 3.2.0-8-virtual x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 19 21:52:06 2012 Ec2AMI: ami-012b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxc (Ubuntu) Importance: Low Status: Confirmed ** Tags: amd64 apport-bug ec2-images precise -- 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/918946 Title: cannot run libvirt in an 'lxc create -t ubuntu' container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918946/+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 918946] Re: cannot run libvirt in an 'lxc create -t ubuntu' container
** Attachment added: libvirt.xml referenced in bug report https://bugs.launchpad.net/bugs/918946/+attachment/2683222/+files/libvirt.xml -- 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/918946 Title: cannot run libvirt in an 'lxc create -t ubuntu' container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918946/+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 918946] Re: cannot run libvirt in an 'lxc create -t ubuntu' container
** Description changed: if you try to start a qemu/kvm guest from inside a container crated by lxc create -t ubuntu, it will fail with something like: error: Failed to start domain my.img error: unable to allow device /dev/full: Operation not permitted - - $ lxc create -t ubuntu -n lv1 + $ lxc-create -t ubuntu -n lv1 + $ lxc-start -n lv1 -d $ lxc-console -n lv1 # login here % apt-get install qemu-kvm % apt-get install dbus # bug 918343 % apt-get install libvirt-bin % qemu-img create -f qcow2 disk.img 1G % virsh define libvirt.xml % virsh start mytest - from a working qemu guest, I see: - # cat /sys/fs/cgroup/devices/libvirt/qemu/myname/devices.list + # cat /sys/fs/cgroup/devices/libvirt/qemu/myname/devices.list c 136:* rw c 1:3 rw c 1:7 rw c 1:5 rw c 1:8 rw c 1:9 rw c 5:2 rw c 254:0 rw So I think we need to add access to that list of devices. (haven't testd this all the way yet). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu5 ProcVersionSignature: User Name 3.2.0-8.15-virtual 3.2.0 Uname: Linux 3.2.0-8-virtual x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 19 21:52:06 2012 Ec2AMI: ami-012b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) -- 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/918946 Title: cannot run libvirt in an 'lxc create -t ubuntu' container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918946/+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 918946] Re: cannot run libvirt in an 'lxc create -t ubuntu' container
** Description changed: if you try to start a qemu/kvm guest from inside a container crated by lxc create -t ubuntu, it will fail with something like: error: Failed to start domain my.img error: unable to allow device /dev/full: Operation not permitted $ lxc-create -t ubuntu -n lv1 $ lxc-start -n lv1 -d $ lxc-console -n lv1 # login here % apt-get install qemu-kvm % apt-get install dbus # bug 918343 % apt-get install libvirt-bin - % qemu-img create -f qcow2 disk.img 1G + % qemu-img create -f qcow2 /tmp/disk.img 1G % virsh define libvirt.xml % virsh start mytest from a working qemu guest, I see: # cat /sys/fs/cgroup/devices/libvirt/qemu/myname/devices.list c 136:* rw c 1:3 rw c 1:7 rw c 1:5 rw c 1:8 rw c 1:9 rw c 5:2 rw c 254:0 rw So I think we need to add access to that list of devices. (haven't testd this all the way yet). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu5 ProcVersionSignature: User Name 3.2.0-8.15-virtual 3.2.0 Uname: Linux 3.2.0-8-virtual x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 19 21:52:06 2012 Ec2AMI: ami-012b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) -- 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/918946 Title: cannot run libvirt in an 'lxc create -t ubuntu' container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918946/+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 918946] Re: cannot run libvirt in an 'lxc create -t ubuntu' container
re-attaching libvirt.xml (this one has full, not relative, path to /tmp/disk.img, and has 'qemu' as the type). ** Description changed: if you try to start a qemu/kvm guest from inside a container crated by lxc create -t ubuntu, it will fail with something like: error: Failed to start domain my.img error: unable to allow device /dev/full: Operation not permitted $ lxc-create -t ubuntu -n lv1 $ lxc-start -n lv1 -d $ lxc-console -n lv1 # login here - % apt-get install qemu-kvm + % apt-get install qemu-kvm wget % apt-get install dbus # bug 918343 % apt-get install libvirt-bin - % qemu-img create -f qcow2 /tmp/disk.img 1G + % wget http://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-x86_64-disk.img -O disk.zimg + % qemu-img convert disk.zimg -O qcow2 /tmp/disk.img % virsh define libvirt.xml % virsh start mytest from a working qemu guest, I see: # cat /sys/fs/cgroup/devices/libvirt/qemu/myname/devices.list c 136:* rw c 1:3 rw c 1:7 rw c 1:5 rw c 1:8 rw c 1:9 rw c 5:2 rw c 254:0 rw So I think we need to add access to that list of devices. (haven't testd this all the way yet). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu5 ProcVersionSignature: User Name 3.2.0-8.15-virtual 3.2.0 Uname: Linux 3.2.0-8-virtual x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 19 21:52:06 2012 Ec2AMI: ami-012b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) ** Attachment removed: libvirt.xml referenced in bug report https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918946/+attachment/2683222/+files/libvirt.xml ** Attachment added: libvirt.xml referenced in bug report https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918946/+attachment/2683440/+files/libvirt.xml ** Description changed: if you try to start a qemu/kvm guest from inside a container crated by lxc create -t ubuntu, it will fail with something like: error: Failed to start domain my.img error: unable to allow device /dev/full: Operation not permitted $ lxc-create -t ubuntu -n lv1 $ lxc-start -n lv1 -d $ lxc-console -n lv1 # login here % apt-get install qemu-kvm wget % apt-get install dbus # bug 918343 % apt-get install libvirt-bin % wget http://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-x86_64-disk.img -O disk.zimg % qemu-img convert disk.zimg -O qcow2 /tmp/disk.img + % wget https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918946/+attachment/2683440/+files/libvirt.xml % virsh define libvirt.xml % virsh start mytest from a working qemu guest, I see: # cat /sys/fs/cgroup/devices/libvirt/qemu/myname/devices.list c 136:* rw c 1:3 rw c 1:7 rw c 1:5 rw c 1:8 rw c 1:9 rw c 5:2 rw c 254:0 rw So I think we need to add access to that list of devices. (haven't testd this all the way yet). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu5 ProcVersionSignature: User Name 3.2.0-8.15-virtual 3.2.0 Uname: Linux 3.2.0-8-virtual x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 19 21:52:06 2012 Ec2AMI: ami-012b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) -- 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/918946 Title: cannot run libvirt in an 'lxc create -t ubuntu' container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918946/+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 918946] Re: cannot run libvirt in an 'lxc create -t ubuntu' container
with the additional /dev/hpet added to the container cgroups, i can successfully boot cirros via lxc from inside the container. -- 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/918946 Title: cannot run libvirt in an 'lxc create -t ubuntu' container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918946/+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 920474] Re: nova client does not work on ubuntu
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/920474 Title: nova client does not work on ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/920474/+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 920474] [NEW] nova client does not work on ubuntu
Public bug reported: It seems that nova-client is currently busted. #!/bin/sh export NOVA_API_KEY=---- export NOVA_USERNAME=smoser export NOVA_PROJECT_ID=smoser_project export NOVA_URL=http://mynova:8774/v1.0/; [ -n $PDIR ] export PYTHONPATH=$PDIR PATH=$PDIR/bin:$PATH exec $@ $ ./ngo nova image-list; echo $? 1 $ git clone https://github.com/rackspace/python-novaclient.git trunk.git $ cd trunk.git $ PDIR=$PWD ../ngo nova image-list out $ sed -n '1,5p;6s/.*/../snip/p;$p' out +-+--+--++ | ID | Name | serverId | Status | +-+--+--++ | 1 | None | | ACTIVE | | 2 | None | | ACTIVE | snip +-+--+--++ ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-novaclient 2012.1~e3~20120111.452-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1 Uname: Linux 3.2.0-10-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Jan 23 09:26:30 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-novaclient UpgradeStatus: Upgraded to precise on 2011-11-07 (77 days ago) ** Affects: python-novaclient (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/920474 Title: nova client does not work on ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/920474/+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 920474] Re: nova client does not work on ubuntu
adding '--version 1.1' or '--version 2' to the nova command line works around issue: nova --version 1.1 image-list -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/920474 Title: nova client does not work on ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/920474/+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 920474] Re: nova client does not work on ubuntu
I can't submit upstream openstack fixes at the moment (waiting on membership to openstack-cla group). Attached is the patch that I think makes sense, and passes for me. ** Patch added: proposed patch https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/920474/+attachment/2689267/+files/920474.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/920474 Title: nova client does not work on ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/920474/+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 920474] Re: nova client requires NOVA_VERSION in environment
** Summary changed: - nova client does not work on ubuntu + nova client requires NOVA_VERSION in environment -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/920474 Title: nova client requires NOVA_VERSION in environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/920474/+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 920474] Re: nova client requires NOVA_VERSION in environment
Submitted upstream at https://review.openstack.org/#change,3312 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/920474 Title: nova client requires NOVA_VERSION in environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/920474/+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 921230] [NEW] presense of kvm-ipxe slows down kvm non-network boot
Public bug reported: $ kvm -boot order=c /tmp/disk.img -curses you'll see somthing like: | | SeaBIOS (version pre-0.6.3-2017_190135-rothera) | | iPXE (http://ipxe.org) 00:03.0 C900 PCI2.10 PnP PMM+17FC94C0+17F894C0 C900 | Press Ctrl-B to configure iPXE (PCI 00:03.0)... That sits there for 2 to 3 seconds (per NIC), and slows boot down by that much. You can work around this by: $ ( rm -Rf x mkdir x cd x ln -sf /usr/share/qemu-kvm/* . rm pxe* ) $ kvm -boot order=c -L x -curses which basically just makes kvm think there are no pxe boot roms, which would be found in /usr/share/qemu-kvm/ as provided by kvm-ipxe. I'd like some way to skip that configure step, since I am explicitly not booting from pxe. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: kvm-ipxe 1.0.0+git-2.149b50-1ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1 Uname: Linux 3.2.0-10-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Tue Jan 24 16:38:01 2012 Dependencies: EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ipxe UpgradeStatus: Upgraded to precise on 2011-11-07 (78 days ago) ** Affects: ipxe (Ubuntu) Importance: Wishlist Status: Confirmed ** Tags: amd64 apport-bug precise running-unity ** Description changed: $ kvm -boot order=c /tmp/disk.img -curses you'll see somthing like: - | + | | SeaBIOS (version pre-0.6.3-2017_190135-rothera) - | + | | iPXE (http://ipxe.org) 00:03.0 C900 PCI2.10 PnP PMM+17FC94C0+17F894C0 C900 | Press Ctrl-B to configure iPXE (PCI 00:03.0)... That sits there for 2 to 3 seconds (per NIC), and slows boot down by that much. You can work around this by: $ ( rm -Rf x mkdir x cd x ln -sf /usr/share/qemu-kvm/* . rm pxe* ) $ kvm -boot order=c -L x -curses which basically just makes kvm think there are no pxe boot roms, which would be found in /usr/share/qemu-kvm/ as provided by kvm-ipxe. + I'd like some way to skip that configure step, since I am explicitly not + booting from pxe. + ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: kvm-ipxe 1.0.0+git-2.149b50-1ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1 Uname: Linux 3.2.0-10-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Tue Jan 24 16:38:01 2012 Dependencies: - + EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all ProcEnviron: - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: ipxe UpgradeStatus: Upgraded to precise on 2011-11-07 (78 days ago) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipxe in Ubuntu. https://bugs.launchpad.net/bugs/921230 Title: presense of kvm-ipxe slows down kvm non-network boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/921230/+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 921794] [NEW] lxc-ls fails as non-root sometimes
Public bug reported: i was using the juju local provider to try to get openstack in juju and came across this bug. Basically, at some point lxc-ls stops working as non-root. ubuntu@ip-10-68-197-170:~$ juju destroy-environment WARNING: this command will destroy the 'jstack' environment (type: local). This includes all machines, services, data, and other resources. Continue [y/N]y 2012-01-25 19:52:53,820 INFO Destroying environment 'jstack' (type: local)... 2012-01-25 19:52:53,821 INFO Destroying unit containers... ubuntu-jstack-0-template ubuntu-jstack-glance-0 ubuntu-jstack-keystone-0 ubuntu-jstack-mysql-0 ubuntu-jstack-nova-cloud-controller-0 ubuntu-jstack-nova-compute-0 ubuntu-jstack-openstack-dashboard-0 ubuntu-jstack-rabbitmq-0 /usr/bin/lxc-ls: line 35: cd: /sys/fs/cgroup/cpuset///lxc: Permission denied ls: cannot access ubuntu-jstack-nova-cloud-controller-0: No such file or directory ls: cannot access ubuntu-jstack-rabbitmq-0: No such file or directory ls: cannot access ubuntu-jstack-keystone-0: No such file or directory ls: cannot access ubuntu-jstack-openstack-dashboard-0: No such file or directory ls: cannot access ubuntu-jstack-glance-0: No such file or directory ls: cannot access ubuntu-jstack-nova-compute-0: No such file or directory ls: cannot access ubuntu-jstack-mysql-0: No such file or directory ubuntu-jstack-0-template ubuntu-jstack-glance-0 ubuntu-jstack-keystone-0 ubuntu-jstack-mysql-0 ubuntu-jstack-nova-cloud-controller-0 ubuntu-jstack-nova-compute-0 ubuntu-jstack-openstack-dashboard-0 ubuntu-jstack-rabbitmq-0 /usr/bin/lxc-ls: line 35: cd: /sys/fs/cgroup/cpuset///lxc: Permission denied ls: cannot access ubuntu-jstack-nova-cloud-controller-0: No such file or directory ls: cannot access ubuntu-jstack-rabbitmq-0: No such file or directory ls: cannot access ubuntu-jstack-keystone-0: No such file or directory ls: cannot access ubuntu-jstack-openstack-dashboard-0: No such file or directory ls: cannot access ubuntu-jstack-glance-0: No such file or directory ls: cannot access ubuntu-jstack-nova-compute-0: No such file or directory ls: cannot access ubuntu-jstack-mysql-0: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu11 ProcVersionSignature: User Name 3.2.0-10.18-virtual 3.2.1 Uname: Linux 3.2.0-10-virtual x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Wed Jan 25 19:53:52 2012 Ec2AMI: ami-0571a76c Ec2AMIManifest: ubuntu-us-east-1/images-testing/ubuntu-precise-daily-amd64-server-20120125.manifest.xml Ec2AvailabilityZone: us-east-1b Ec2InstanceType: m1.xlarge Ec2Kernel: aki-825ea7eb Ec2Ramdisk: unavailable ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- 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/921794 Title: lxc-ls fails as non-root sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/921794/+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 921794] Re: lxc-ls fails as non-root sometimes
-- 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/921794 Title: lxc-ls fails as non-root sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/921794/+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 921921] [NEW] add support to lxc tools for cloning with btrfs snapshots
Public bug reported: lxc-clone should be able to do the clone via lxc snapshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1 Uname: Linux 3.2.0-10-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Wed Jan 25 22:53:25 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to precise on 2011-11-07 (79 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/921921 Title: add support to lxc tools for cloning with btrfs snapshots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/921921/+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 921921] Re: add support to lxc tools for cloning with btrfs snapshots
-- 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/921921 Title: add support to lxc tools for cloning with btrfs snapshots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/921921/+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 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
On Thu, 26 Jan 2012, Clint Byrum wrote: Excerpts from Noah's message of Thu Jan 26 11:26:08 UTC 2012: You can achieve this with a cloud-init userdata section by specifying the apt mirror. This is all that is needed: #cloud-config apt_mirror: http://uk.archive.ubuntu.com/ubuntu/ Noah was pointing out that cloud-init in 10.04 does not have that option, so ... you kind of need to hack with 'sed' there. -- 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/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+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 922241] [NEW] lxc should Suggest or Recommend btrfs-tools
Public bug reported: After my last patch, adding btrfs support, we should at least Suggest 'btrfs-tools'. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu13 ProcVersionSignature: User Name 3.2.0-10.18-virtual 3.2.1 Uname: Linux 3.2.0-10-virtual x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Thu Jan 26 18:37:53 2012 Ec2AMI: ami-0130 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxc (Ubuntu) Importance: Low Assignee: Serge Hallyn (serge-hallyn) Status: Triaged ** Tags: amd64 apport-bug ec2-images precise -- 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/922241 Title: lxc should Suggest or Recommend btrfs-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/922241/+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 922241] Re: lxc should Suggest or Recommend btrfs-tools
** Changed in: lxc (Ubuntu) Status: New = Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided = Low ** Changed in: lxc (Ubuntu) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/922241 Title: lxc should Suggest or Recommend btrfs-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/922241/+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 922241] Re: lxc should Suggest or Recommend btrfs-tools
Serge, just pick this up in your next lxc update. -- 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/922241 Title: lxc should Suggest or Recommend btrfs-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/922241/+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 912066] Re: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present.
** Changed in: cloud-init (Ubuntu) Status: New = Invalid ** Changed in: cloud-init Status: New = Invalid -- 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/912066 Title: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/912066/+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 924375] [NEW] cloud-init should allow pre-seeding of ec2 datasource:Ec2:metadata_urls
Public bug reported: it would be best if cloud-init supported pre-seeding of the ec2 metadata url. This way, something coordinating the installation could cleanly specify through a preseed the location of the metadata url. It might also make sense to be able to pre-seed 'manual_cache_clean'. Then, you could essentially pre-seed cloud-config that looked like: manual_cache_clean: True datasource: Ec2: metadata_urls: [ http://192.168.1.131:80/abcdefg ] where the path was a uuid or something, and on subsequent boots cloud-init would not need that url to be present. Note, though, that 'manual_cache_clean' is less important here, because you could easily have cloud-config or cloud-init data served by the metadata service populate that value in /etc/cloud/cloud.cfg.d. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/924375 Title: cloud-init should allow pre-seeding of ec2 datasource:Ec2:metadata_urls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/924375/+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 925110] Re: lxc-ls fails as non-root sometimes (second bug)
-- 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/925110 Title: lxc-ls fails as non-root sometimes (second bug) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925110/+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 925110] [NEW] lxc-ls fails as non-root sometimes (second bug)
Public bug reported: ubuntu@server-4390:~$ lxc-ls; echo $? ubuntu-jstack-0-template ubuntu-jstack-nova-compute-0 ubuntu-jstack-glance-0 ubuntu-jstack-nova-volume-0 ubuntu-jstack-keystone-0 ubuntu-jstack-openstack-dashboard-0 ubuntu-jstack-mysql-0 ubuntu-jstack-rabbitmq-0 ubuntu-jstack-nova-cloud-controller-0 ubuntu-source /usr/bin/lxc-ls: line 35: cd: /sys/fs/cgroup/cpuset///lxc: Permission denied ls: cannot access ubuntu-jstack-nova-volume-0: No such file or directory ls: cannot access ubuntu-jstack-nova-cloud-controller-0: No such file or directory ls: cannot access ubuntu-jstack-rabbitmq-0: No such file or directory ls: cannot access ubuntu-jstack-keystone-0: No such file or directory ls: cannot access ubuntu-jstack-openstack-dashboard-0: No such file or directory ls: cannot access ubuntu-jstack-glance-0: No such file or directory ls: cannot access ubuntu-jstack-nova-compute-0: No such file or directory ls: cannot access ubuntu-jstack-mysql-0: No such file or directory 2 ubuntu@server-4390:~$ sudo lxc-ls; echo $? ubuntu-jstack-0-template ubuntu-jstack-nova-compute-0 ubuntu-jstack-glance-0 ubuntu-jstack-nova-volume-0 ubuntu-jstack-keystone-0 ubuntu-jstack-openstack-dashboard-0 ubuntu-jstack-mysql-0 ubuntu-jstack-rabbitmq-0 ubuntu-jstack-nova-cloud-controller-0 ubuntu-source ubuntu-jstack-glance-0 ubuntu-jstack-nova-compute-0 ubuntu-jstack-keystone-0 ubuntu-jstack-nova-volume-0 ubuntu-jstack-mysql-0 ubuntu-jstack-openstack-dashboard-0 ubuntu-jstack-nova-cloud-controller-0 ubuntu-jstack-rabbitmq-0 0 2 things are causing this failure. a.) 'mount -t cgroup' just seems to show nothing (no idea why) b.) /sys/fs/cgroup/*/lxc are root only readable $ ls -l /sys/fs/cgroup/cpuacct/ | egrep (libvirt|lxc) drwxr-xr-x 4 root root 0 Feb 1 19:55 libvirt drwx-- 10 root root 0 Feb 1 20:28 lxc Things to fix: * need trailing / on 'ls -l' (in case its a symlink). * figure out why those directories are read-only ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Wed Feb 1 15:30:12 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to precise on 2011-11-07 (86 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/925110 Title: lxc-ls fails as non-root sometimes (second bug) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925110/+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 924195] Re: cannot report ubuntu-bug -w on isag window
** Package changed: sysstat (Ubuntu) = apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to sysstat in Ubuntu. https://bugs.launchpad.net/bugs/924195 Title: cannot report ubuntu-bug -w on isag window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/924195/+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 898373] Re: fsck.ext3: Device or resource busy while trying to open /dev/xvda2
Seen again at [1] from tests for precise alpha-2 at [2] -- [1] https://jenkins.qa.ubuntu.com/view/Precise/job/precise-server-ec2/ARCH=i386,REGION=us-west-2,STORAGE=instance-store,TEST=cloud-config,label=ubuntu-server-ec2-testing/lastBuild/artifact/None/i386/m1.small/instance-store/i-e688ccd6/uec2-20120202-1453-d28473559d2145-terminated.console.txt [2] https://jenkins.qa.ubuntu.com/job/precise-server-ec2/3/ARCH=i386,REGION=us-west-2,STORAGE=instance-store,TEST=cloud-config,label=ubuntu-server-ec2-testing/ -- 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/898373 Title: fsck.ext3: Device or resource busy while trying to open /dev/xvda2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/898373/+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 926160] [NEW] precise cloud-images significantly larger than oneiric
Public bug reported: See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase. This compares what I found on ubuntu-oneiric-11.10-arch-server-20120108 ubuntu-precise-daily-arch-server-20120202 The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows: -- | 11.10 | prec | %growth amd64 disk.img | 218M | 228M | 4.8 amd64 .tar.gz_ | 207M | 217M | 4.6 amd64 ebs df__ | 762M | 973M | 27.6 amd64 inst df_ | 655M | 823M | 25.6 i386_ disk.img | 198M | 210M | 6.0 i386_ .tar.gz_ | 188M | 200M | 6.3 i386_ ebs df__ | 689M | 814M | 18.1 i386_ inst df_ | 582M | 753M | 29.3 (Note, precise df numers are from daily build 20120108, 1 day after alpha2) I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem). So i have the following separate issues raised from above: * why such a dramatic growth between 11.10 and 12.04 current * can we/should we get the EBS filesystem usage more in line with instance-store? * Why the vast outlier below in increased usage of ebs for a given release-arch: oneiric-amd64: 16% oneiric-i386: 18% precise-amd64: 18% precise-i386: 8% ** Affects: ubuntu Importance: Medium Assignee: Ubuntu Server Team (ubuntu-server) Status: Confirmed ** Tags: cloud-images ec2-images -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/926160 Title: precise cloud-images significantly larger than oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/926160/+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 926160] Re: precise cloud-images significantly larger than oneiric
** Attachment added: data collected from each of the 8 instances i ran. https://bugs.launchpad.net/bugs/926160/+attachment/2710789/+files/data-collected.tar.gz ** Description changed: See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase. This compares what I found on -ubuntu-oneiric-11.10-arch-server-20120108 -ubuntu-precise-daily-arch-server-20120202 + ubuntu-oneiric-11.10-arch-server-20120108 + ubuntu-precise-daily-arch-server-20120202 The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows: -- | 11.10 | prec | %growth amd64 disk.img | 218M | 228M | 4.8 - amd64 .tar.gz | 207M | 217M | 4.6 - amd64 ebs df | 762M | 973M | 27.6 - amd64 inst df | 655M | 823M | 25.6 + amd64 .tar.gz_ | 207M | 217M | 4.6 + amd64 ebs df__ | 762M | 973M | 27.6 + amd64 inst df_ | 655M | 823M | 25.6 i386_ disk.img | 198M | 210M | 6.0 - i386_ .tar.gz | 188M | 200M | 6.3 - i386_ ebs df | 689M | 814M | 18.1 - i386_ inst df | 582M | 753M | 29.3 + i386_ .tar.gz_ | 188M | 200M | 6.3 + i386_ ebs df__ | 689M | 814M | 18.1 + i386_ inst df_ | 582M | 753M | 29.3 (Note, precise df numers are from daily build 20120108, 1 day after alpha2) I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem). So i have the following separate issues raised from above: - * why such a dramatic growth between 11.10 and 12.04 current - * can we/should we get the EBS filesystem usage more in line with instance-store? - * Why the vast outlier below in increased usage of ebs for a given release-arch: -oneiric-amd64: 16% -oneiric-i386: 18% -precise-amd64: 18% -precise-i386: 8% + * why such a dramatic growth between 11.10 and 12.04 current + * can we/should we get the EBS filesystem usage more in line with instance-store? + * Why the vast outlier below in increased usage of ebs for a given release-arch: + oneiric-amd64: 16% + oneiric-i386: 18% + precise-amd64: 18% + precise-i386: 8% -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/926160 Title: precise cloud-images significantly larger than oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/926160/+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 926160] Re: precise cloud-images significantly larger than oneiric
Note, the automatic running of 'apt-get update' had run on the amd64 precise instance, so that data was tainted. I changed the bug description to accommodate and picked up a new instancen data to replace it. That is in this tarball. ** Description changed: See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase. This compares what I found on ubuntu-oneiric-11.10-arch-server-20120108 ubuntu-precise-daily-arch-server-20120202 The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows: -- | 11.10 | prec | %growth amd64 disk.img | 218M | 228M | 4.8 amd64 .tar.gz_ | 207M | 217M | 4.6 - amd64 ebs df__ | 762M | 973M | 27.6 + amd64 ebs df__ | 762M | 883M | 15.8 amd64 inst df_ | 655M | 823M | 25.6 i386_ disk.img | 198M | 210M | 6.0 i386_ .tar.gz_ | 188M | 200M | 6.3 i386_ ebs df__ | 689M | 814M | 18.1 i386_ inst df_ | 582M | 753M | 29.3 (Note, precise df numers are from daily build 20120108, 1 day after alpha2) I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem). So i have the following separate issues raised from above: * why such a dramatic growth between 11.10 and 12.04 current * can we/should we get the EBS filesystem usage more in line with instance-store? - * Why the vast outlier below in increased usage of ebs for a given release-arch: + * Why the change in increased usage of ebs for a given release-arch: oneiric-amd64: 16% oneiric-i386: 18% - precise-amd64: 18% + precise-amd64: 7.2% precise-i386: 8% ** Attachment added: fixed data collected https://bugs.launchpad.net/ubuntu/+bug/926160/+attachment/2710853/+files/data-collected.tar.gz -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/926160 Title: precise cloud-images significantly larger than oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/926160/+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 926160] Re: precise cloud-images significantly larger than oneiric
** Description changed: See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase. This compares what I found on ubuntu-oneiric-11.10-arch-server-20120108 ubuntu-precise-daily-arch-server-20120202 The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows: -- | 11.10 | prec | %growth amd64 disk.img | 218M | 228M | 4.8 amd64 .tar.gz_ | 207M | 217M | 4.6 + amd64 file tot | 559M | 575M | 2.9 amd64 ebs df__ | 762M | 883M | 15.8 amd64 inst df_ | 655M | 823M | 25.6 i386_ disk.img | 198M | 210M | 6.0 i386_ .tar.gz_ | 188M | 200M | 6.3 + i386_ file tot | 484M | 505M | 4.3 i386_ ebs df__ | 689M | 814M | 18.1 i386_ inst df_ | 582M | 753M | 29.3 - (Note, precise df numers are from daily build 20120108, 1 day after - alpha2) + (Note, precise df numers are from daily build 20120108, 1 day after alpha2) + 'file tot' is result of 'du --total --one-file-system --apparent-size'. I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem). So i have the following separate issues raised from above: * why such a dramatic growth between 11.10 and 12.04 current * can we/should we get the EBS filesystem usage more in line with instance-store? * Why the change in increased usage of ebs for a given release-arch: oneiric-amd64: 16% oneiric-i386: 18% precise-amd64: 7.2% precise-i386: 8% -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/926160 Title: precise cloud-images significantly larger than oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/926160/+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 927744] [NEW] rotate around round robin hosts is not configurable
Public bug reported: In conversation about apt-mirrors at http://irclogs.ubuntu.com/2012/02/06/%23ubuntu-server.html#t16:57 lifeless said: lifeless oh lifeless someone should really file a bug (if they haven't) about squid rotating between round-robin hosts too much lifeless or at least there being no knob lifeless there are valid reasons to want slow rotation in the client lifeless that is definitely something we(squid) should support tuning of I'm sure lifeless can elaborate on what those valid reasons are, and it is known that this would not actually fix the apt issue. This is a result of issues where Release / Packages.gz is grabbed from one server in ubuntu mirrors and the other grabbed from another and they're not consistent. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: squid3 3.1.14-1ubuntu0.1 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Mon Feb 6 17:16:27 2012 Ec2AMI: ami-00e5 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: standard.xlarge Ec2Kernel: aki-00e4 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: squid3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.squid3.squid.conf: 2012-02-02T21:27:49.342780 ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images oneiric -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/927744 Title: rotate around round robin hosts is not configurable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/927744/+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 927744] Re: rotate around round robin hosts is not configurable
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/927744 Title: rotate around round robin hosts is not configurable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/927744/+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 901881] Re: nova and glance should depend on python-keystone
** Summary changed: - nova should depend on python-keystone + nova and glance should depend on python-keystone -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/901881 Title: nova and glance should depend on python-keystone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glance/+bug/901881/+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 926160] Re: precise cloud-images significantly larger than oneiric
** Changed in: ubuntu Assignee: Ubuntu Server Team (ubuntu-server) = Ben Howard (utlemming) -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/926160 Title: precise cloud-images significantly larger than oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/926160/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-p-cloudutils] Improvements to cloud-utils and Related Packages
Blueprint changed by Scott Moser: Whiteboard changed: Etherpad: edit: http://pad.ubuntu.com/uds-p-servercloud-p-cloudutils time slider: http://pad.ubuntu.com/ep/pad/view/uds-p-servercloud-p-cloudutils/latest Work Items: Update ubuntu-cloudimg-query to read /query2 data: TODO Update cloud-publish-ubuntu to read /query2 data: TODO implement cloud-images-sync: TODO Update cloud-publish-image for nova API: TODO Update cloud-publish-tarball for nova API: TODO - consult upstream on euca2ools upgrade: TODO - consult upstream on boto upgrade: TODO - euca2ools upstream sync: TODO - boto upstream sync: TODO + consult upstream on euca2ools upgrade: DONE + consult upstream on boto upgrade: DONE + euca2ools upstream sync: DONE + boto upstream sync: DONE [racb] merge his changes with cloud-stash-sandbox: TODO - consider joining cloud-stash-sandbox to cloud-utils: TODO + consider joining cloud-stash-sandbox to cloud-utils: POSTPONED -- Improvements to cloud-utils and Related Packages https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloudutils -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-p-cloudimages-cloudinit] Improvements to Cloud-init or Cloud Images
Blueprint changed by Scott Moser: Whiteboard changed: Etherpad: edit: http://pad.ubuntu.com/uds-p-servercloud-p-cloudimages-cloudinit time slider: http://pad.ubuntu.com/ep/pad/view/uds-p-servercloud-p-cloudimages-cloudinit/latest Work Items: Implement public glance server: TODO Canonical IS ticket for public glance server: TODO Populate glance server on build finish: TODO Provide clean /query2 data pointing to .img files: TODO hand off glance server to canonical IS: TODO [smoser] make ec2-publishing-scripts publish instance-store concurrently: DONE [smoser] make ec2-publishing-scripts publish ebs concurrently: DONE [smoser] make ec2-publishing-scripts describe-images much less (speed): DONE [smoser] add serial number to daily HEADER.html output: DONE [smoser] trouble shoot publish parallel fallout as it comes in: DONE [smoser] re-implement EBS publishing to not require ssh or elastic IP: TODO sync/merge with upstream cdimage scripts and nectarine: TODO cloud-init fix /etc/hosts editing (bug 871966, bug 890501): DONE - cloud-init upstream add unit test: TODO + cloud-init upstream add unit test: DONE cloud-init support userdata, metadata from configdrive (bug 857378): TODO cloud-init support network config via configdrive: TODO cloud-init support cloud-local mirrors via dns naming convention: DONE cloud-init support cloud-local proxy via dns naming convention: TODO better documentation rebundling via user-data and kvm: TODO follow up with aligouri on definitive qcow format link for OVF: DONE -- Improvements to Cloud-init or Cloud Images https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloudimages-cloudinit -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-p-cloudimages-cloudinit] Improvements to Cloud-init or Cloud Images
Blueprint changed by Scott Moser: Whiteboard changed: Etherpad: edit: http://pad.ubuntu.com/uds-p-servercloud-p-cloudimages-cloudinit time slider: http://pad.ubuntu.com/ep/pad/view/uds-p-servercloud-p-cloudimages-cloudinit/latest Work Items: Implement public glance server: TODO Canonical IS ticket for public glance server: TODO Populate glance server on build finish: TODO Provide clean /query2 data pointing to .img files: TODO hand off glance server to canonical IS: TODO [smoser] make ec2-publishing-scripts publish instance-store concurrently: DONE [smoser] make ec2-publishing-scripts publish ebs concurrently: DONE [smoser] make ec2-publishing-scripts describe-images much less (speed): DONE [smoser] add serial number to daily HEADER.html output: DONE [smoser] trouble shoot publish parallel fallout as it comes in: DONE [smoser] re-implement EBS publishing to not require ssh or elastic IP: TODO sync/merge with upstream cdimage scripts and nectarine: TODO cloud-init fix /etc/hosts editing (bug 871966, bug 890501): DONE cloud-init upstream add unit test: DONE cloud-init support userdata, metadata from configdrive (bug 857378): TODO cloud-init support network config via configdrive: TODO cloud-init support cloud-local mirrors via dns naming convention: DONE cloud-init support cloud-local proxy via dns naming convention: TODO - better documentation rebundling via user-data and kvm: TODO + better documentation rebundling via user-data and kvm: DONE + automated script based rebundling via user-data and kvm: TODO + automated script based rebundling via user-data and chroot: TODO follow up with aligouri on definitive qcow format link for OVF: DONE -- Improvements to Cloud-init or Cloud Images https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloudimages-cloudinit -- Ubuntu-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 897303] Re: bacula-common-mysql uninstallable due to conflicting files
** Changed in: bacula (Ubuntu) Assignee: (unassigned) = Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/897303 Title: bacula-common-mysql uninstallable due to conflicting files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/897303/+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 913009] Re: package bacula-common-mysql (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/bacula/libbaccats.la', which is also in package bacula-common 5.2.1-0ubuntu2
*** This bug is a duplicate of bug 897303 *** https://bugs.launchpad.net/bugs/897303 ** This bug has been marked a duplicate of bug 897303 bacula-common-mysql uninstallable due to conflicting files -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/913009 Title: package bacula-common-mysql (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/bacula/libbaccats.la', which is also in package bacula-common 5.2.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/913009/+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 928834] Re: nova-compute depends on qemu-kvm, even if kvm is not used
This was by design, as a fix for bug 833530 (needs qemu-img) We may be able to remove that dependency now that we have qemu-utils package. ** Changed in: nova (Ubuntu) Status: New = Triaged ** Changed in: nova (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/928834 Title: nova-compute depends on qemu-kvm, even if kvm is not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/928834/+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 898373] Re: fsck.ext3: Device or resource busy while trying to open /dev/xvda2
** Description changed: I'm opening this against cloud-init, but I do not actually think that is valid. In an ec2 instance for test of alpha-1 images [1], we saw errors on boot like: - Loading, please wait... - [1342606.840604] udevd[81]: starting version 175 - Begin: Loading essential drivers ... done. - Begin: Running /scripts/init-premount ... done. - Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. - Begin: Running /scripts/local-premount ... done. - [1342607.148903] EXT4-fs (xvda1): mounted filesystem with ordered data mode. Opts: (null) - Begin: Running /scripts/local-bottom ... done. - done. - Begin: Running /scripts/init-bottom ... done. - lxcmount stop/pre-start, process 178 - fsck from util-linux 2.19.1 - fsck from util-linux 2.19.1 - fsck: fsck.swap: not found - fsck: Error 2 while executing fsck.swap for /dev/xvda3 - fsck.ext3: Device or resource busy while trying to open /dev/xvda2 - Filesystem mounted or opened exclusively by another program? - cloud-init start-local running: Wed, 30 Nov 2011 19:25:20 +. up 3.98 seconds - no instance data found in start-local + Loading, please wait... + [1342606.840604] udevd[81]: starting version 175 + Begin: Loading essential drivers ... done. + Begin: Running /scripts/init-premount ... done. + Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. + Begin: Running /scripts/local-premount ... done. + [1342607.148903] EXT4-fs (xvda1): mounted filesystem with ordered data mode. Opts: (null) + Begin: Running /scripts/local-bottom ... done. + done. + Begin: Running /scripts/init-bottom ... done. + lxcmount stop/pre-start, process 178 + fsck from util-linux 2.19.1 + fsck from util-linux 2.19.1 + fsck: fsck.swap: not found + fsck: Error 2 while executing fsck.swap for /dev/xvda3 + fsck.ext3: Device or resource busy while trying to open /dev/xvda2 + Filesystem mounted or opened exclusively by another program? + cloud-init start-local running: Wed, 30 Nov 2011 19:25:20 +. up 3.98 seconds + no instance data found in start-local The swap errors are due to bug 898365. The cloud-config given to the instance included: - mounts: -- [ ephemeral0, /opt , auto, defaults,noexec ] -- [ swap, null ] + mounts: + - [ ephemeral0, /opt , auto, defaults,noexec ] + - [ swap, null ] And given that bug, the /etc/fstab during this reboot probably had: - /dev/xvda2 /opt auto defaults,noexec,comment=cloudconfig 0 2 - /dev/xvda3 None auto defaults,nobootwait,comment=cloudconfig 0 2 + /dev/xvda2 /opt auto defaults,noexec,comment=cloudconfig 0 2 + /dev/xvda3 None auto defaults,nobootwait,comment=cloudconfig 0 2 The thing that confuses me, and the reason I do not think this is cloud- init's fault is that this happens prior to cloud-init start-local. So, yes, there is a broken fstab, but not for /dev/xvda2. The errors listed above are on first reboot after cloud-init wrote those fstab entries, and then issued 'mount -a' from a upstart job (cloud-config.conf) launched at: -start on (filesystem and started rsyslog) + start on (filesystem and started rsyslog) -- [1] https://jenkins.qa.ubuntu.com/job/precise-server-ec2/ARCH=i386,REGION=us-west-1,STORAGE=instance-store,TEST=cloud-config,label=ubuntu-server-ec2-testing/1/artifact/None/i386/m1.small/instance-store/i-835a3dc4/uec2-2030-1920-5d6ee3bc489541-terminated.console.txt ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cloud-init 0.6.2-0ubuntu1 [modified: usr/share/pyshared/cloudinit/CloudConfig/cc_mounts.py] ProcVersionSignature: User Name 3.2.0-2.5-virtual 3.2.0-rc3 Uname: Linux 3.2.0-2-virtual i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Wed Nov 30 21:44:25 2011 Ec2AMI: ami-a7cc07ce Ec2AMIManifest: ubuntu-us-east-1/images-testing/ubuntu-precise-daily-i386-server-2030.manifest.xml Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) + + + Related bugs: + * bug 928990: fsck / dirty filesystem on instance is death -- 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/898373 Title: fsck.ext3: Device or resource busy while trying to open /dev/xvda2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/898373/+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 928990] [NEW] fsck / dirty filesystem on instance is death
Public bug reported: As we saw in bug 898373, if a filesystem needs manual intervention for an fsck, then boot completely stops. mountall will wait indefinitely on someone attending to this broken filesystem, and in a cloud (at least in EC2) with no console access, that means the system will never boot. I discussed this in #ubuntu-devel with slangasek at http://irclogs.ubuntu.com/2012/02/02/%23ubuntu-devel.html#t16:54. He suggested to mark disk 'noauto' or 'nobootwait', but that is not really what someone would want to do. The ideal fix in some sense would be to start an ssh daemon, and force the user into a screen session where they could fix it. To that, slangasek said: smoser: sure, either fixing /etc/init/mountall-shell.conf to support this, or diverting it in a cloud-specific job, seems reasonable there Related bugs: * bug 898373 : fsck.ext3: Device or resource busy while trying to open /dev/xvda2 ** Affects: cloud-init (Ubuntu) Importance: High Status: Triaged ** Tags: cloud-images ec2-images -- 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/928990 Title: fsck / dirty filesystem on instance is death To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/928990/+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 923179] Re: package bacula-common-mysql (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/bacula/libbaccats.la', which is also in package bacula-common 5.2.3-0ubuntu2
*** This bug is a duplicate of bug 897303 *** https://bugs.launchpad.net/bugs/897303 ** This bug has been marked a duplicate of bug 897303 bacula-common-mysql uninstallable due to conflicting files -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/923179 Title: package bacula-common-mysql (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/bacula/libbaccats.la', which is also in package bacula-common 5.2.3-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/923179/+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 897303] Re: bacula-common-mysql uninstallable due to conflicting files
I've just uploaded a fix for this. I've verified installation of the packages, but kept the version at 5.2.3. I'd very much appreciate someone testing that the packages work (I have no real experience with bacula). If someone would like to request or tackle the merge to upstream 5.2.5, then please open a bug (note, a local 'bzr merge-upstream' seemed to go OK). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/897303 Title: bacula-common-mysql uninstallable due to conflicting files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/897303/+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 929523] [NEW] bacula-director does not start, dummy libbaccats
Public bug reported: On 5.2.3-0ubuntu3, reported from bug 897303. The latest package installed When attempting to start the bacula-director the following error is logged, and the service does not start. 08-Feb 18:59 bacula-dir JobId 0: Fatal error: Please replace this dummy libbaccats library with a proper one. 08-Feb 18:59 bacula-dir JobId 0: Fatal error: Could not open Catalog MyCatalog, database ;. 08-Feb 18:59 bacula-dir ERROR TERMINATION ** Affects: bacula (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/929523 Title: bacula-director does not start, dummy libbaccats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/929523/+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 897303] Re: bacula-common-mysql uninstallable due to conflicting files
Sandy, Thank you for the report. I opened bug 929523 to track your issue in comment 5. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/897303 Title: bacula-common-mysql uninstallable due to conflicting files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/897303/+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 929523] Re: bacula-director does not start, dummy libbaccats
just for the record, to get the correct libbaccats installed, I've just changed debian/rules like: === modified file 'debian/rules' --- debian/rules2012-01-19 00:13:55 + +++ debian/rules2012-02-09 14:25:48 + @@ -203,9 +203,10 @@ dh_install -pbacula-console -pbacula-console-qt cp $(DEFAULTINSTALLDIR)/usr/sbin/bconsole debian/bacula-console/usr/sbin/bacula-console cp debian/tmp-build-$(DEFAULTVARIANT)/src/qt-console/.libs/bat debian/bacula-console-qt/usr/bin/bat - cp debian/tmp-build-mysql/src/cats/.libs/libbaccats-$(MAINVER).so debian/tmp-install-mysql/usr/lib/bacula - cp debian/tmp-build-sqlite3/src/cats/.libs/libbaccats-$(MAINVER).so debian/tmp-install-sqlite3/usr/lib/bacula - cp debian/tmp-build-pgsql/src/cats/.libs/libbaccats-$(MAINVER).so debian/tmp-install-pgsql/usr/lib/bacula + cp debian/tmp-build-mysql/src/cats/.libs/libbaccats-*$(MAINVER).so debian/tmp-install-mysql/usr/lib/bacula + cp debian/tmp-build-sqlite3/src/cats/.libs/libbaccats-*$(MAINVER).so debian/tmp-install-sqlite3/usr/lib/bacula + cp debian/tmp-build-pgsql/src/cats/.libs/libbaccats-*$(MAINVER).so debian/tmp-install-pgsql/usr/lib/bacula + # dbconfig-common stuff # $(call ext-upgrade-all,7_to_8,1.36.0) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/929523 Title: bacula-director does not start, dummy libbaccats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/929523/+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 929523] Re: bacula-director does not start, dummy libbaccats
bacula has mulitple implementors of the libbaccats.so (pgsql, sqlite3, mysql). It seems like the right place for this library is in the bacula- common-variant package. After one change to get the correct libbaccats-variant-version.so copied in, I have layout like: /usr/lib/bacula/libbaccats-5.2.3.so - libbaccats-mysql-5.2.3.so /usr/lib/bacula/libbaccats-mysql-5.2.3.so /usr/lib/bacula/libbaccats-mysql.so - libbaccats-mysql-5.2.3.so /usr/lib/bacula/libbaccats.so - libbaccats-5.2.3.so However, doing that results in dpkg-shlibeps complaining and failing as : | dh_shlibdeps -pbacula-sd-mysql -Lbacula-common-mysql | dpkg-shlibdeps: warning: debian/bacula-common-mysql/usr/lib/bacula/libbaccats-5.2.3.so has an unexpected SONAME (libbaccats-mysql-5.2.3.so) | dpkg-shlibdeps: error: no dependency information found for debian/bacula-common-mysql/usr/lib/bacula/libbaccats-5.2.3.so (used by debian/bacula-sd-mysql/usr/bin/bscan). | dh_shlibdeps: dpkg-shlibdeps -Tdebian/bacula-sd-mysql.substvars -Sdebian/bacula-common-mysql debian/bacula-sd-mysql/usr/bin/bcopy debian/bacula-sd-mysql/usr/bin/bscan debian/bacula-sd-mysql/usr/sbin/btape returned exit code 2 | make: *** [binary-arch-common] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 I'm not sure how to work around this, because bacula is certainly intending to provide the file libbaccats-mysql-5.2.3.so as libbaccats-5.2.3.so. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/929523 Title: bacula-director does not start, dummy libbaccats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/929523/+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 929523] Re: bacula-director does not start, dummy libbaccats
@Sandy, Could you please put this through some test? I've verified the mysql daemon installs and starts. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/929523 Title: bacula-director does not start, dummy libbaccats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/929523/+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
