** Tags removed: uec-images
** Tags added: azure cloud-images
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1193380
Title:
resource disk mounted at /mnt/resource should be
Public bug reported:
If you attempt to run 'waagent -daemon -verbose', it will fail, and
you'll find (in /var/log/waagent.log):
2013/06/21 15:32:29 ERROR:Traceback (most recent call last):
2013/06/21 15:32:29 ERROR: File /usr/sbin/waagent, line 2572, in module
2013/06/21 15:32:29 ERROR:
David,
I'm pretty sure the answer to your question about ownership of that file is
that ownership by the package has no effect on config-file upgrade prompt. I'm
not 100% certain, but I know that in the cloud images, /etc/default/grub has
been a pain for us in this respect, and it also does
Public bug reported:
when starting instances on azure, there is a fair chance (seems more
likely for some users thanothers) that the instance will fail to reach
provisioned state.
I do not have a a good guess as to why this is.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: walinuxagent
as I'm trying to debug this instance that failed for me, and then came up after
a 'vm restart', there is no indication that / was ever mounted RW the first
time. Ie, there is no evidence in /var/log of *anything* having run.
cloud-init starts on mounted MOUNTPOINT=/
and logs pretty much
given my previous comment, i would have suspected that there was disk or kernel
failure.
however, ssh-keyscan seemed to indicate ssh was running:
$ ssh-keyscan us-west-1.cloudapp.net
# us-west-1.cloudapp.net SSH-2.0-OpenSSH_6.1p1 Debian-4
Connection closed by 137.135.115.232
--
You received
Public bug reported:
Hi, it seems that walinux-agent may be run during the build process. I
suspect this because when I got into an instance that was restarted and
came up after showoing bug 1195524, I saw timestamps in
/var/log/walinux.
Heres an example:
2013/06/21 04:33:47 WARNING:Moved
the solution here is to block jobs from running on 'apt-get install'.
the build process for cloud-images does this.
the way to prevent is to put something like this in /usr/sbin/policy-
rc.d (taken from VMBuilder/plugins/ubuntu/templates/nostart-policy-
rc.d.tmpl )
while true; do
case $1 in
** Attachment added: waagent.log and waagent dir.
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1195524/+attachment/3717115/+files/waagent-info.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in
ok. so i have 2 other systems that are showing this failure now.
I was able to ssh into them, though.
walinux-agent had provisioned the user, populated ssh keys and then also
started sshd (which it actually should not do).
it shouldn't start sshd because it is possibly doing that before sshd
has
ok... i think ihave a reasonable description of what caused this specific hang.
The last entry in this /var/log/waagent.log was:
2013/06/28 14:50:12 Provisioning image using OVF settings in the DVD.
2013/06/28 14:50:12 Resource disk (/dev/sdb1) is mounted at /mnt/resource with
fstype ext4
I'm fairly certain there is still a race condition that I described comment 8.
Please raise the hostname issue in another bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
In the future, we plan to have simplestreams data to describe kernels available.
this is part of the work for maas this cycle.
https://code.launchpad.net/~smoser/maas/netinst2ss is some code i put together
to scrape archive.ubuntu.com and put it into simplestreams format.
for the moment, the
(Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Precise)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu Precise)
Importance: Undecided = High
** Changed in: cloud-init (Ubuntu Precise)
Assignee: (unassigned) = Scott Moser (smoser
)
** Affects: cloud-init (Ubuntu)
Importance: Medium
Assignee: Scott Moser (smoser)
Status: Fix Released
** Affects: cloud-init (Ubuntu Precise)
Importance: High
Assignee: Scott Moser (smoser)
Status: Triaged
** Tags: amd64 apport-bug precise
--
You received
This was fixed in walinuxagent at 1.3.2-0ubuntu3.
** Also affects: walinuxagent (Ubuntu)
Importance: Undecided
Status: New
** Changed in: walinuxagent (Ubuntu)
Importance: Undecided = Medium
** Changed in: walinuxagent (Ubuntu)
Status: New = Fix Released
--
You received
** Also affects: walinuxagent (Ubuntu Saucy)
Importance: Undecided
Assignee: Ben Howard (utlemming)
Status: Fix Released
** Also affects: walinuxagent (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: walinuxagent (Ubuntu Precise)
Status: New =
We've put a ppa at https://launchpad.net/~azure-cloud-builds/+archive/sru
apt-add-repository -y ppa:azure-cloud-builds/sru
--
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/1202202
Public bug reported:
$ sudo hostname
sudo: unable to resolve host smfoo3
smfoo3
I think that this is because we've disabled MonitorHostName in
walinuxagent.
that code would actually:
* get the hostname of the system
* monitor every X seconds for changs in the output of 'hostname'
* if
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
** Changed in: cloud-init (Ubuntu)
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.
Public bug reported:
This came up when talking with Soren on IRC.
We can now attach a OVF CDrom and seed cloud-init that way, but it would be
nice to be able to do the same with a more friendly disk format.
Ie, if there were a disk (cdrom or disk) that had:
* LABEL=cloudinit
* user-data
*
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided = Medium
** Changed in: cloud-init
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu)
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided = Medium
** Changed in: cloud-init
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu)
: High
Assignee: Scott Moser (smoser)
Status: In Progress
** Affects: cloud-init (Ubuntu Oneiric)
Importance: High
Assignee: Scott Moser (smoser)
Status: In Progress
** Tags: apport-bug ec2-images i386 oneiric
--
You received this bug notification because you
** Changed in: cloud-init (Ubuntu)
Milestone: None = ubuntu-11.10
** Changed in: cloud-init (Ubuntu)
Status: New = In Progress
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = High
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Scott Moser (smoser
Public bug reported:
This is a feature request to include support for configuring landscape-
client via cloud-config syntax.
The syntax would look something like:
#cloud-config
landscape:
account-name: foobar
title: cloud1
secret: hiya
ProblemType: Bug
DistroRelease: Ubuntu
https://review.openstack.org/#change,631
** Changed in: nova
Status: New = In Progress
** Changed in: nova
Assignee: (unassigned) = Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu
I can confirm this, and also confirm it on 11.04. I suspect it is the
case with even 10.04.
$ env LC_ALL=en_GB.UTF-8 ssh 10.55.60.59 'cat /etc/cloud/build.info; echo ===;
locale'
bash: warning: setlocale: LC_ALL: cannot change locale (en_GB.UTF-8)
build_name: server
serial: 20110426
===
locale:
*** This bug is a duplicate of bug 857021 ***
https://bugs.launchpad.net/bugs/857021
sorry, this is dupe of bug 857021.
** This bug has been marked a duplicate of bug 857021
glance (2011.3-0ubuntu1) fails to install, error in .postinst
--
You received this bug notification because you
fix-commited see comment 3.
** Changed in: nova
Status: In Progress = Fix Committed
--
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/854614
Title:
metadata service
Public bug reported:
On a freshly installed system, I ran:
apt-get install -y cloud-utils euca2ools glance nova-api nova-common
nova-compute-lxc nova-doc nova-network nova-objectstore nova-scheduler
python-greenlet python-mysqldb python-nova rabbitmq-server unzip qemu-kvm
$ ls -l /etc/nova/
** Changed in: nova (Ubuntu)
Importance: Undecided = Low
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
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/861459
Title:
Public bug reported:
nova has 'FLAGS.max_nbd_devices' :
flags.DEFINE_integer('max_nbd_devices', 16,
'maximum number of possible nbd devices')
However,
a.) that doesn't really tell you why you care about this number, even though it
effectively limits the number of lxc
--
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/861504
Title:
nova-compute-lxc limited by available nbd devices to 16
To manage notifications about this bug go to:
Now that i'm thinking a bit more, maybe it would make sense to not have
the flag in nova for 'FLAGS.max_nbd_devices'.
Instead, it could just go through /dev/nbd* or /sys/block/nbd* and get a
list that way.
** Also affects: nova
Importance: Undecided
Status: New
--
You received this
** Summary changed:
- nova-compute-lxc limited by available nbd devices to 16
+ nova-compute-lxc limited by available nbd devices to 16 instances
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Assignee: (unassigned) = Scott Moser (smoser)
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu
I am curious, though, you actually have cloud instances that take 60
seconds for a dhcp to come up? That is a *huge* portion of general
time to use.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
On Thu, 29 Sep 2011, James E. Blair wrote:
But because cloud-init-nonet only checks to see if the ifstate file is
updated, it exits immediately.
That is no longer the case. cloud-init now waits for the
static-network-up event. That event will only occur after the dhcp
receives an address
I'm marking this as invalid. It was mostly user error on my part.
I've got an improved version of the script here at
https://gist.github.com/1169889
** Changed in: nova (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server
** Tags added: server-o-nrs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/863629
Title:
libvirt-lxc: virFileOpenTtyAt can't be called on /some/other/dev/pts
To manage
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Importance: Undecided = High
** Changed in: nova (Ubuntu)
Status: New = Confirmed
** Changed in: nova (Ubuntu)
Milestone: None = ubuntu-11.10
** Tags added: server-o-rs
--
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Milestone: None = ubuntu-11.10
** Changed in: nova (Ubuntu)
Status: New = Confirmed
** Changed in: nova (Ubuntu)
Importance: Undecided = High
--
You received this bug
** Changed in: nova (Ubuntu)
Milestone: None = ubuntu-11.10
--
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/859587
Title:
nova-network deletes default route
To manage
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Milestone: None = ubuntu-11.10
** Changed in: nova (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Public bug reported:
Following previous documentation I'd seen in the natty time frame, and are also
documented at lxc upstream (http://lxc.teegra.net/), I had a line like the
following in /etc/fstab:
none /cgroups cgroup defaults 0 0
Then, I found out about cgroup-bin, and thought that
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubuntu.
https://bugs.launchpad.net/bugs/869364
Title:
cgconfig gets confused with /cgroups fstab entry
To manage notifications about this bug go to:
I'm not sure what ends up doing the unclean unmount of /cgroup when you try to
start cgconfig, but an strace of
/usr/sbin/cgconfigparser -l /etc/cgconfig.conf
shows:
stat64(/sys/fs//cgroup/cpu, 0xbfb057c0) = -1 ENOENT (No such file or
directory)
mkdir(/sys, 0775) = -1
Public bug reported:
I launched an instance on a nova cloud, and it was unreachable.
Upon investigation of the console log, I found:
| cloud-init start-local running: Thu, 06 Oct 2011 19:57:29 +. up 4.02
seconds
| no instance data found in start-local
| ci-info: lo: 1 127.0.0.1
** Attachment added: console output of first boot (failed)
https://bugs.launchpad.net/bugs/869492/+attachment/2519592/+files/console-first-boot.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
I can reproduce this from inside this instance with the following program:
#!/usr/bin/python
import urllib2, sys, socket
def doget(iurl, timeout):
reason = None
try:
req = urllib2.Request(iurl)
resp = urllib2.urlopen(req, timeout=timeout)
except urllib2.HTTPError as e:
Public bug reported:
Ubuntu is carrying a patch nova-manage_flagfile_location.patch, for quite some
time.
(timestamp: Tue 2010-11-23 12:17:09 +0100)
I've just noticed that if you try to run out of a source directory with
that patch applied and without specifying --flagfile, that you will
I suggest we replace the current 'nova-manage_flagfile_location.patch'
with this one.
We should also try to get this upstream.
The change here is basically to try to use /etc/nova/nova.conf only if it
exists and is readable.
While that still will break you if you're running nova-manage from a
This is borderline of low and wishlist.
uncloud-init should not be used. It is really a legacy hack.
We need to
a.) change documentation at https://help.ubuntu.com/community/UEC/Images to not
reference uncloud-init
b.) provide tools or documentation to use the fully functional and more easily
fixed in revision 460.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New = Fix Committed
** Changed in: cloud-init
Importance: Undecided = Low
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
--
You received
Hi,
I've just uploaded a ppa build of nova to
https://launchpad.net/~smoser/+archive/ppa with a patch pulled back from trunk
which is reported to fix this issue.
Could someone listening here please try to with my ppa build and report back
if that fixes your problem.
To do this, simply
bas-t,
https://code.launchpad.net/~smoser/nova/lp838581/+merge/78528
has the changes i made.
We've
--
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/838581
Title:
Failures in db_pool
gethostbyname(hostname) is non-determinable.
there could be multiple responses. and indeterminable order.
--
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
I now know how I I was hitting this.
On my local system, I would log, open a terminal and and then run a bip proxy
with:
ssh -o ControlPath=none -C -L 7778:localhost:7778 -f -N ${HOST}
I can replicate that same behavior by ssh'ing to a system, then doing:
sleep 30m disown; exit
After that,
On Tue, 11 Oct 2011, Clint Byrum wrote:
Excerpts from Scott Moser's message of Tue Oct 11 00:18:27 UTC 2011:
gethostbyname(hostname) is non-determinable.
there could be multiple responses. and indeterminable order.
Agreed, which is precisely why I believe cloud-init must leave the FQDN
Just for reference, Serge posted to libc-alpha mailing list at
http://www.cygwin.com/ml/libc-alpha/2011-10/threads.html#9
(multiple devpts mounts not supported
insysdeps/unix/sysv/linux/ptsname.c:_ptsname_internal())
--
You received this bug notification because you are a member of Ubuntu
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Scott Moser (smoser)
--
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/833499
Title:
virt/disk.py unconditionally inserts
Just to be clear on status here, this is fix-released in oneiric.
It has been uploaded to archive in -proposed for maverick and natty, but we are
waiting on someone to verify it before it will enter -updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Chuck submitted a merge proposal for fixing this at
https://review.openstack.org/#change,891 .
--
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/833519
Title:
lxc in nova will happily
I suspect that this is related to bug 876458.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/875950
Title:
/var/run/dnsmasq/resolv.conf empty on boot
To manage notifications about
Public bug reported:
$ sudo apt-get --purge remove rabbitmq-server
0 upgraded, 0 newly installed, 1 to remove and 5 not upgraded.
After this operation, 1,790 kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 29070 files and directories currently installed.)
Public bug reported:
$ ssh SOMEHOST sh -c '{ sudo apt-get install -y rabbitmq-server; echo
FINISHED; } | tee my.log'
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
rabbitmq-server
debconf: unable to initialize
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/878600
Title:
'service start rabbitmq-server' does not fully detach from parent
To manage notifications about this bug go to:
** Summary changed:
- 'apt-get install rabbitmq | tee' from an ssh connection hangs
+ 'service start rabbitmq-server' does not fully detach from parent
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
Once rabbitmq-server had been installed, I can reproduce this with:
$ ssh $host sudo service rabbitmq-server start
Ie, no 'tee' is necessary.
This, however, does not exhibit the hang:
$ sudo service rabbitmq-server start out 21
This patch seems to fix it for me:
---
** Summary changed:
- 'service start rabbitmq-server' does not fully detach from parent
+ service start rabbitmq-server' does not fully detach from parent
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
Dave,
I hit this when trying to use an ubuntu git branch as the source of the nova
component for devstack.
Because of this bug, i wasted time figuring out what was going wrong, rather
than spending that time figuring out whether or not an issue with trunk applied
to Ubuntu. It is probably
** Bug watch added: Debian Bug tracker #646175
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646175
** Also affects: rabbitmq-server (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646175
Importance: Unknown
Status: Unknown
--
You received this bug notification
Blueprint changed by Scott Moser:
Whiteboard set to:
Ideas for cloud-init:
* simpler ovf-like transport (ie, simple iso or disk image attached to image
triggers running)
* release an 0.6.2
* get fedora patchset included into 0.6.3
Ideas for cloud images:
* Better rebundling through local
Blueprint changed by Scott Moser:
Whiteboard changed:
Ideas for cloud-init:
- * simpler ovf-like transport (ie, simple iso or disk image attached to image
triggers running)
- * release an 0.6.2
- * get fedora patchset included into 0.6.3
+ * simpler ovf-like transport (ie, simple iso
Blueprint changed by Scott Moser:
Whiteboard set to:
New function in cloud-utils:
* native nova import (using glance) through cloud-publish-image or
cloud-publish-tarball
* sync-from-cloud-images
utility that would basically mirror cloud-images.ubuntu.com to your locally
configured cloud
Blueprint changed by Scott Moser:
Whiteboard changed:
Ideas for cloud-init:
* simpler ovf-like transport (ie, simple iso or disk image attached to image
triggers running)
* release an 0.6.2
* get fedora patchset included into 0.6.3
-
Ideas for cloud images:
* Better
Blueprint changed by Scott Moser:
Whiteboard set to:
* [smoser] i'd like to hvae devstack working from ubuntu packages proper (as
opposed to git source)
alternatively, at least make devstack usable when using the ubuntu package
branches (maybe need to add bzr support to devstack
** Bug watch added: Debian Bug tracker #646473
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646473
** Also affects: rabbitmq-server (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646473
Importance: Unknown
Status: Unknown
--
You received this bug notification
--
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/880984
Title:
error resizing root filesystem
To manage notifications about this bug go to:
Public bug reported:
I launched a cloud-image of precise on openstack and saw in cloud-init
log:
011-10-24 17:12:45,578 - cc_resizefs.py[DEBUG]: resizing root filesystem
(type=ext4, maj=253, min=1)
2011-10-24 17:12:45,582 - cc_resizefs.py[WARNING]: Failed to resize filesystem
(['resize2fs',
This is reproducible well after boot, with:
$ sudo resize2fs /dev/vda1
resize2fs 1.42-WIP (9-Oct-2011)
Filesystem at /dev/vda1 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 1
resize2fs: Inappropriate ioctl for device While checking for on-line resizing
support
Note a few things:
a.) /dev/vda has has been grown during first boot, its partition table rewritten
GROWROOT: CHANGED: partition=1 start=16065 old: size=4176900 end=4192965
new: size=20948760,end=20964825
$ sudo sfdisk -g /dev/vda
/dev/vda: 20805 cylinders, 16 heads, 63 sectors/track
Just noticed i was not comparing ubuntu version to debian version of
the same. We're behind debian by 7 days in a WIP snapshot, that
changelog contained:
e2fsprogs (1.42~WIP-2011-10-16-1) unstable; urgency=low
* New upstream release
* Fix online resizing with resize2fs (Closes: #644989)
more info. I booted an oneiric system with userdata containing :
#cloud-config
cloud_init_modules:
- bootcmd
- set_hostname
- update_hostname
- update_etc_hosts
- rsyslog
- ssh
Essentially that stops cloud-init from doing the resize2fs on boot, so I
can subsequently install other packages
** Changed in: e2fsprogs (Ubuntu)
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/880984
Title:
error resizing root filesystem
Public bug reported:
Given the script script, I would expect that out.raw* files would
be bit for bit identical. And indeed, a little test image I made, they were.
However, when I tried it on a oneiric compressed qcow disk, they were not.
With 'in' of oneiric-server-cloudimg-amd64-disk1.img,
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/882197
Title:
data loss in conversion to or from vpc
To manage notifications about this bug go to:
Just to test whether it was reading or writing that was the error, I tried this:
$ qemu-img info /tmp/convtest.vpc
image: /tmp/convtest.vpc
file format: vpc
virtual size: 2.0G (2147991552 bytes)
disk size: 645M
The size there is incorrect, and identical to what the size of the
target is after
This bug seems at least related :
https://bugzilla.redhat.com/show_bug.cgi?id=528678 .
** Bug watch added: Red Hat Bugzilla #528678
https://bugzilla.redhat.com/show_bug.cgi?id=528678
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This is fixed in revision 437.
** Changed in: cloud-init
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/832175
Title:
Doesn't report an
There was some discussion on this, but i believe the only real way to
fix it is to add locales to the image.
--
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/859814
Title:
Locale
** Changed in: cloud-init
Status: Triaged = 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/861866
Title:
cloud-init-nonet does not wait for dhcp
To manage
Fixed in trunk revision 448
** 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/850206
Title:
cloud-init should
fix-released in revision 418 on trunk, 0.6.1-0ubuntu14
** Changed in: cloud-init (Ubuntu)
Status: Triaged = Fix Released
** Changed in: cloud-init
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: cloud-init
Importance: Undecided = Low
** Changed in: cloud-init
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/848932
Title:
fixed in upstream revision 463.
** Changed in: cloud-init
Status: Triaged = 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
** Changed in: cloud-init
Status: Fix Committed = 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/812646
Title:
Race in DataSourceNoCloudNet with kvm
To
** Changed in: cloud-init
Status: Fix Committed = 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/819507
Title:
consume_userdata is only called once per
** Changed in: cloud-init
Status: Fix Committed = 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/812539
Title:
FQDN does not get set correctly in /etc/hosts
201 - 300 of 11836 matches
Mail list logo
