I just updated and still have a hanging wget:
...
Setting up kdepim-runtime (4:4.7.1-0ubuntu3) ...
Setting up libcouchdb-glib-1.0-2 (0.7.4-0ubuntu2) ...
Setting up libdesktopcouch-glib-1.0-2 (0.7.4-0ubuntu2) ...
Setting up oneconf (0.2.6.4) ...
Setting up software-center (4.1.23.4) ...
Updating
Unfortunately killing the wget in a loop is now not continuing the
eucalyptus start job. Also calling 'sudo stop eucalyptus' failed to
change anything, the eucalyptus start job is hanging.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The error seems to have been transient. I killed the hanging eucalyptus
postinst process and I got no further hang.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/851611
Title:
** Changed in: apt (Ubuntu)
Status: New = Confirmed
--
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/813400
Title:
lxc-create -t ubuntu complains about /dev/pts
To manage
We tried the following to overcome the problem, nothing was successful:
1) Restart eucalyptus-cc
2) Reboot front-end and node-controlle
3) Purge and reinstall eucalyptus-cc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Public bug reported:
Today's upgrade to eucalyptus blocks on my system:
Setting up unity-lens-applications (0.4.6-0ubuntu1) ...
Setting up unity-lens-files (0.6.6-0ubuntu1) ...
Setting up compiz-fusion-plugins-main (1:0.9.5.94+bzr20110915-0ubuntu1) ...
Setting up eucalyptus-admin-tools
apport information
** Attachment added: EucalyptusCCLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411458/+files/EucalyptusCCLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: EucalyptusCloudOutputLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411460/+files/EucalyptusCloudOutputLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
apport information
** Attachment added: EucalyptusCloudDebugLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411459/+files/EucalyptusCloudDebugLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: EucalyptusAxis2cLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411457/+files/EucalyptusAxis2cLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: eucalyptus.local.conf.txt
https://bugs.launchpad.net/bugs/851611/+attachment/2411464/+files/eucalyptus.local.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: EucalyptusHTTPDErrorLog.gz
https://bugs.launchpad.net/bugs/851611/+attachment/2411461/+files/EucalyptusHTTPDErrorLog.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: eucalyptus.conf.txt
https://bugs.launchpad.net/bugs/851611/+attachment/2411463/+files/eucalyptus.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
apport information
** Attachment added: EucalyptusInstalledVersions.txt
https://bugs.launchpad.net/bugs/851611/+attachment/2411462/+files/EucalyptusInstalledVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus
I confirm James finding, I have the wget running as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/851611
Title:
Oneiric: Upgrade to 2.0.1+bzr1256 blocks
To manage
For the record, I killed the post instll script 'eucalyptus-
common.postinst', leaving eucalyptus unconfigured to proceed working on
the system.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
The problem exists on the Ubuntu 10.10 training cloud as well. Maybe a
packaging error?
** Changed in: eucalyptus (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
Public bug reported:
I'm running tests and launch rather large numbers of instances on a UEC
running with Ubuntu 10.04 LTS. I discovered that instances regularly
fail to start and it seems to be that they never get a network address
assigned. In the cc.log I discovered the following entries:
Another fail during tonight's test run:
[Thu Mar 3 01:36:43 2011][011910][EUCADEBUG ] RunInstances(): running instance
i-49AF07C3 with emiId emi-0CE515A7...
[Thu Mar 3 01:36:43 2011][011910][EUCAERROR ] vnetAddHost(): failed to add
host d0:0d:49:AF:07:C3 on vlan 10
[Thu Mar 3 01:36:43
For completeness the network definition of the cloud. If wanted I can
grant ssh access to the system:
VNET_MODE=MANAGED-NOVLAN
VNET_SUBNET=172.19.0.0
VNET_NETMASK=255.255.0.0
VNET_DNS=172.24.1.1
VNET_ADDRSPERNET=32
VNET_PUBLICIPS=172.24.129.136
Again, when starting new instances it works and
And another one:
[Thu Mar 3 11:48:55 2011][011912][EUCADEBUG ] RunInstances(): running instance
i-3393055A with emiId emi-0CE515A7...
[Thu Mar 3 11:48:55 2011][011912][EUCAERROR ] vnetAddHost(): failed to add
host d0:0d:33:93:05:5A on vlan 10
[Thu Mar 3 11:48:55 2011][011912][EUCADEBUG ]
The problem seems to occur quite randomly, here the statistics from the
last 5 test runs:
Started: 25 Clients, 4 Servers.
Stopped: 21
Started: 340 Clients, 27 Servers.
Stopped: 360
Started: 70 Clients, 8 Servers.
Stopped: 71
Started: 70 Clients, 5 Servers.
Stopped: 68
Started: 30 Clients, 6
From time to time I see these timeouts, could they be related?
4 0 8
path=/services/Eucalyptus/?AWSAccessKeyId=WKy3rMzOWPouVOxK1p3Ar1C2uRBwa2FBXnCwA
ction=TerminateInstancesInstanceId.1=i-47F10968InstanceId.2=i-4D930877Instanc
I wonder if the timeout for the termination request leads to a situation
when the pool of network addresses gets empty. Is there a way to see the
internal IP address allocation?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The only work around for the problem seems to be to terminate instances
and then try again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
https://bugs.launchpad.net/bugs/728018
Title:
10.04 LTS: Failure to
Did you enable the accessibility of the instance ports via
euca-authorize? What is the output of euca-describe-groups for the
clouds admin user?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
Public bug reported:
I've created a new cloud using the install from packages method. The
first unusual thing was that the CC was not automatically registered,
even when running on the same host as the CLC. Now the next problem
manifests in the node not being registered due to missing keys:
$
Nope, I didn't do that before hand. I copied it after it failed. But it
seems it's then to late already. I still don't quite understand how the
keys can be missing - I thought they are setup when registering a
cluster. I also believe this is where it went wrong.
--
Not all keys present
I created a new cloud and this time via packaged install and this time
the keys were present after registering the cluster controller. Please
close this bug as it cannot be reproduced.
--
Not all keys present
https://bugs.launchpad.net/bugs/592648
You received this bug notification because you
Is the cluster registered in the cloud at all? Do you see it with
euca-describe-availability-zones?
--
eucalyptus-cc and uec-component-listener services are not started
https://bugs.launchpad.net/bugs/598182
You received this bug notification because you are a member of Ubuntu
Server Team, which
@Carlos,
the cloud of the error reports is long gone. If need be I can try to
recreate the problem on a new one next week.
--
euca-create-volume fails at times with Error communicating with Storage
Controller
https://bugs.launchpad.net/bugs/517086
You received this bug notification because you
Here we go, the problem is fixed:
$ for i in $(seq 1 32); do euca-create-volume -s 1 -z TorstenCloud; done
$ euca-describe-volumes | grep avail | wc -l
30
$ euca-describe-volumes | grep creat | wc -l
0
$ euca-describe-volumes | grep fail | wc -l
2
$ for i in $(euca-describe-volumes | cut -c8-20
I can reproduce the problem on the training cloud:
$ for i in `seq 1 100`; do euca-create-volume -z TorstenCloud -s1; done
...
VOLUME vol-52B905E31 creating2010-09-02T06:27:50.814Z
VOLUME vol-5F2906521 creating2010-09-02T06:27:51.142Z
VOLUME vol-598F062A
Public bug reported:
When I start an instance with --addressing-private option, associate an
elastic IP to it and take this away later, the instance claims another
public ip instead of staying private.
$ euca-describe-instances
RESERVATION r-3B69071E spindlerdefault
INSTANCE
It's Eucalyptus 1.6.2 on Ubuntu 10.04.1.
--
instances gets public ip address after disassociate-address
https://bugs.launchpad.net/bugs/660055
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
** Summary changed:
- instances gets public ip address after disassociate-address
+ [10.04] instances gets public ip address after disassociate-address
--
[10.04] instances gets public ip address after disassociate-address
https://bugs.launchpad.net/bugs/660055
You received this bug
Public bug reported:
The default security group of a user can not be deleted with admin
privileges. E.g.
$ euca-describe-groups | grep davidchen
GROUP davidchen default default group
PERMISSION davidchen default ALLOWS tcp 22 22 FROM
CIDR 0.0.0.0/0
There
Public bug reported:
Binary package hint: kvm
I've updated my kernel on an Ubuntu 10.04 host with linux-image-generic-
pae-lts-backport-maverick. Since then two virtual machines using Lucid
do no longer start. The boot hangs with an empty screen and a _
displayed on the top left. When I reboot
Public bug reported:
Build Version/Date: 1.6~bzr931-0ubuntu7
Environment used for testing: Ubuntu Karmic RC
Summary: After purging and removing /var/lib/eucalyptus image store is
out of sync
Steps to Reproduce: Install UEC from packages, call aptitude purge on
eucalyptus-[cc,cloud,sc,walrus],
Public bug reported:
Build Version/Date: 1.6~bzr931-0ubuntu7
Environment used for testing: Ubuntu Karmic RC
Summary: After purging and removing /var/lib/eucalyptus image store is
out of sync
Steps to Reproduce: Install UEC from packages, call aptitude purge on
eucalyptus-[cc,cloud,sc,walrus],
On Mon, 2009-10-26 at 16:20 +, Mathias Gug wrote:
Could you try to purge python-image-store-proxy as well?
To properly purge a UEC install I'd recommend to purge eucalyptus-
common.
I purged both and reinstalled UEC. Now Firefox can't get to
https://127.0.0.1:8443 anymore.
--
After
This is from /var/log/eucalyptus/httpd-cc_error_log
[Mon Oct 26 18:20:47 2009] [notice] caught SIGTERM, shutting down
[Mon Oct 26 18:22:33 2009] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0
configured -- resuming normal operations
[Mon Oct 26 18:22:36 2009] [error] server reached MaxClients
According to cloud-debug.log there is a FileNotFoundException for
startup.groovy. I apt-file search'ed it and found it in
eucalyptus-java-common. But re-installing eucalyptus-java-common did not
succeed in getting the file back.
Excerpt from cloud-debug.log:
password less login works:
eucalyp...@beaufighter:~$ ssh typhoon
Linux typhoon 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009
x86_64
To access official Ubuntu documentation, please visit:
http://help.ubuntu.com/
System information as of Tue Oct 27 09:59:37 CET 2009
System
Public bug reported:
On Karmic RC and eucalyptus 1.6~bzr931-0ubuntu7 :
spind...@beaufighter:~$ euca_conf --no-rsync --discover-nodes
WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable,
path=/, member=Introspect
Failed to resolve service '192.168.1.103' of type
Copying the keys manually and adding typhoon to the nodes list in
eucalyptus.conf solved the problem.
--
discover-nodes fails on scp'ing keys
https://bugs.launchpad.net/bugs/461746
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
When running in SYSTEM networking mode on Karmic, Eucalyptus
1.6~bzr931-0ubuntu7, I get the following error in httpd-nc_error.log:
ERROR: Disallowed command //usr/share/eucalyptus/populate_arp.pl
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status:
Console output for failed start attempt.
** Attachment added: console-output
http://launchpadlibrarian.net/34665954/console-output
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification because you are a member of Ubuntu
Server Team,
On Fri, 2009-10-30 at 10:50 +, Thierry Carrez wrote:
Sounds like an error in image bundling/registration then. What steps did
you follow to upload the image ?
https://help.ubuntu.com/community/UEC/BundlingImages
The only option I left out is the -r $IARCH
--
Official UEC image fails to
Here the relevant parts from history:
535 euca-bundle-image --kernel true -i karmic-uec-amd64-vmlinuz-virtual
536 euca-upload-bundle -m /tmp/karmic-uec-amd64-vmlinuz-virtual.manifest.xml
537 euca-upload-bundle -m /tmp/karmic-uec-amd64-vmlinuz-virtual.manifest.xml
-b karmic-uec-kernel
This is the jaunty-scripts.manifest as found in the
/var/lib/eucalyptus/bukkits/jaunty-scripts directory.
** Attachment added: jaunty-scripts.manifest
http://launchpadlibrarian.net/34939324/jaunty-scripts.manifest
--
ec2-bundle-vol and ec2-upload-bundle result in non accepted manifest
I haven't saved the history, sorry. I followed these steps:
sudo apt-get install default-jre ruby libopenssl-ruby curl rsync unzip
installed ec2-api and ec2-ami tools
rm /root/firstboot_done
mount ephemeral storage to /mnt
copy X.509 zip to /mnt, create .euca directory there
set JAVA_HOME
put
Public bug reported:
After re-bundling the official Karmic UEC image, it fails to boot:
17 name=/usr/sbin/tcpdump
Done.
Done.
mount: mount point /var/run does not exist
mountall: mount /var/run [334] terminated with status 32
mountall: Filesystem could not be mounted: /var/run
mount: mount point
Here the complete console output. The image was generated with
euca-bundle-vol
euca-upload-bundle
euca-register
** Attachment added: console.output
http://launchpadlibrarian.net/35442427/console.output
--
Re bundled karmic image fails to boot
https://bugs.launchpad.net/bugs/479621
You
On Tue, 2009-11-10 at 08:51 +, Eric Hammond wrote:
Torsten: What AMI id are you starting with?
This one was a Jaunty image created with vmbuilder.
part file looks like:
root 2000
swap 1
and first boot looks like:
while (! ping -c 1 archive.ubuntu.com); do sleep 1; done
apt-get -y install
Public bug reported:
After creating a homemade Karmic image with vmbuilder, it fails to
register with:
euca-register karmic-homemade/root.img.manifest.xml
Warning: failed to parse error message from AWS: unknown:1:49: syntax error
Traceback (most recent call last):
File /usr/bin/euca-register,
Here the relevant parts from history:
64 export http_proxy=http://10.153.104.60:3128
65 sudo vmbuilder xen ubuntu
66 sudo vmbuilder xen ubuntu --part ./part --firstboot ./firstboot
67 ls
68 euca-bundle-image -i ubuntu-xen/root.img
69 euca-upload-bundle -m
Here the image manifest.
** Attachment added: root.img.manifest.xml
http://launchpadlibrarian.net/35480755/root.img.manifest.xml
--
euca-register fails with syntax error
https://bugs.launchpad.net/bugs/480048
You received this bug notification because you are a member of Ubuntu
Server Team,
This might be unrelated to euca-register, I get the same error with
euca-describe-availability-zones:
$ euca-describe-availability-zones
Warning: failed to parse error message from AWS: unknown:1:49: syntax error
Traceback (most recent call last):
File
After a reboot, 'euca-describe-availability-zones verbose' worked fine.
'euca-register' still fails, with a different error:
$ euca-register karmic-homemade/root.img.manifest.xmlWarning: failed to parse
error message from AWS: unknown:1:0: syntax error
EC2ResponseError: 403 Forbidden
Failure:
After a wait the last error went away and euca-register worked.
--
euca-register fails with syntax error
https://bugs.launchpad.net/bugs/480048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
I tried both. ec2-register from the instance initially and then euca-
register from the front end.
--
ec2-bundle-vol and ec2-upload-bundle result in non accepted manifest
https://bugs.launchpad.net/bugs/470355
You received this bug notification because you are a member of Ubuntu
Server Team,
This seems to be cloud specific to the one at my home. I have the image
running on a different cloud and it works fine there.
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification because you are a member of Ubuntu
Server Team, which is
grep -i deadlock /var/log/eucalyptus/* /tmp/deadlock
** Attachment added: deadlock
http://launchpadlibrarian.net/35653868/deadlock
--
euca-register fails with syntax error
https://bugs.launchpad.net/bugs/480048
You received this bug notification because you are a member of Ubuntu
Server
At the moment not, as I do not have access to that cloud environment any
longer. From UDS I take that we do not fully support the separation of
cloud and cluster controller in UEC. This needs to be done by changing
the eucalyptus.conf files.
--
eucalyptus-cloud not starting when separating cloud
Public bug reported:
When using the services tab in the UEC webUI and registering with
Landscape, the 8443 port is suggested instead of the correct 8773.
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
Wrong URL port suggested for Landscape registration
Public bug reported:
A question that came up in every UEC class I've run so far was how to
make the cloud and cluster controller redundant, so the cloud is more
resilient to failures of those components. Are there any suggestions out
there how to achieve this?
** Affects: eucalyptus (Ubuntu)
Public bug reported:
I just installed UEC with the Lucid installer. First I installed the
front end with clc, walrus, cc and sc. Then the node. The node told me
that it cannot find walrus and the installer suggested to me to install
it first.
I checked ps aux | grep avahi on the frontend and
Public bug reported:
The default Ubuntu kernel provides only 8 loopback devices. Setting more
is possible with the max_loop=number on the kernel boot parameters
line in /boot/grub/grub.cfg. It would be great if this can be done
automagically for a host configured as Storage Controller.
I just learned that the number of loop back devices is managed
dynamically by the kernel. However, the number of actual loop back
devices in /dev/ is set to 8 by default. Creating new ones can be done
with
$ sudo mknod b 7 number /dev/loopnumber
--
Maximum number of 8 loopback devices low for
I cannot repeat the problem today.
After specifying the hostname to 'node01' the next screeen says 'Select
cloud installation mode' and informs that no eucalyptus cloud controller
was found on your network. Albeit the cloud controller is up and running
on another machine. I then specify the cloud
I've seen similar problems in the past, but waiting for some extended
time (15 minutes) solved it. In that time the Web UI was also not
working, the admin user was reported to not exist.
--
eucalyptus-cloud doesn't reply to requests
https://bugs.launchpad.net/bugs/503180
You received this bug
I cannot reproduce the problem anymore with the cloud I've got currently
running. I suggest to invalidate the bug.
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
On UEC on Ubuntu 9.10 the following problem occured during last week's
training session:
A student created a key and it worked fine. After some time it stopped
working, e.g. the key can no longer be used to log into an instance. The
key is named mykey and specific for a
Public bug reported:
During the UEC class this week using Ubuntu 9.10 the following problem
surfaced:
The cloud was fully operational. The networking mode was changed from
MANAGED_NOVLAN to SYSTEM. After rebooting the front-end and node no
instance could be started anymore. The instance was left
*** This bug is a duplicate of bug 464384 ***
https://bugs.launchpad.net/bugs/464384
The complete cloud (frontend and node) was rebooted.
--
Changing networking mode left cloud non working
https://bugs.launchpad.net/bugs/514203
You received this bug notification because you are a member of
On Fri, 2010-01-29 at 19:26 +, Dustin Kirkland wrote:
...
Or, rather, did they create and use instances with that key, and then
later, create instances but not be able to use that key?
This I meant with stopped working.
--
SSH key stopped working
https://bugs.launchpad.net/bugs/514198
You
*** This bug is a duplicate of bug 464384 ***
https://bugs.launchpad.net/bugs/464384
You are right, it is a duplicate, the following worked:
$ sudo restart eucalyptus CLEAN=1
--
Changing networking mode left cloud non working
https://bugs.launchpad.net/bugs/514203
You received this bug
The sshd is started, the last few lines from euca-get-console-output:
ec2:
ec2: #
ec2: -BEGIN SSH HOST KEY FINGERPRINTS-
ec2: 2048 c5:e6:f6:21:16:bf:b4:d8:00:fa:1b:ad:29:12:86:de
/etc/ssh/ssh_host_rsa_key.pub (RSA)
ec2: 1024
From the extra tab select 'Register this cloud with Landscape'
** Attachment added: UEC-landscape-start.png
http://launchpadlibrarian.net/38613962/UEC-landscape-start.png
--
Wrong URL port suggested for Landscape registration
https://bugs.launchpad.net/bugs/491437
You received this bug
From there the Landscape registration form is filled in incorrectly with
the port 8443.
** Attachment added: UEC-landscape-wrongURL.png
http://launchpadlibrarian.net/38613978/UEC-landscape-wrongURL.png
--
Wrong URL port suggested for Landscape registration
Quite possible, the students are instructed to create a key called
'mykey' in the exercise. With this the problem can be reproduced:
$ euca-add-keypair mykey2 mykey2.priv
$ euca-add-keypair mykey2 mykey2.priv
$ euca-run-instances -t c1.medium -k mykey2 emi-DF481077
$ ssh -i mykey2.priv
Public bug reported:
Happened on the Ubuntu training cloud with Ubuntu 9.10.
For testing purposes for training I create 32 volumes with the following script:
for i in $( seq 1 32); do sleep 5; euca-create-volume -s 1 -z classcloud; done
After creating these I remove them with:
for vol in
On Tue, 2010-02-09 at 21:39 +, Boris Devouge wrote:
- ran on 3 nodes: 'sudo apt-get clean all sudo apt-get update
sudo
apt-get upgrade'
Any reason for using this method rather than the recommended
do-release-upgrade -d
procedure?
--
UEC upgrade from 9.10 karmic to Lucid fails
I first reproduced the problem on the training cloud, then installed the
PPA packages. The problem went away, the cloud is responsive within the
first two minutes of restarting the frontend.
--
eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after
reboot or services restart
I enabled karmic-proposed, installed eucalyptus-*-1.6~bzr931-0ubuntu7.5
on the training cloud in the datacenter. I rebooted node and frontend
and the cloud was operational from the start. I started an instance and
ssh'ed to it. All looks good and operational.
--
[SRU] eucalyptus-cloud doesn't
Public bug reported:
I made a mistake when trying to attach a volume to an instance and gave
it device /dev/sda. Instead of failing gracefully the node stopped to
operate. Here's the log:
[Tue Feb 23 15:14:48 2010][001762][EUCAINFO ] started VM instance i-3B530725
[Tue Feb 23 15:18:13
Restarting libvirtd seemed to resolve the issue, albeit state is
inconsistent thereafter.
--
[karmic]: attaching volume to /dev/sda results in non operational node
https://bugs.launchpad.net/bugs/526506
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
I installed a frontend and node with the alpha3 server CD. Frontend works fine,
but
$ euca-describe-availability-zones verbose
does not have any node. I tried
$ euca_conf --discover-nodes --no-rsync
but the node was not discovered. I added it then by hand to
The following command did not give an error for me on Lucid Alpha 3, 2010-03-01
updates installed:
$ qemu-img snapshot -c toast ./lucid.qcow2
Version: 0.12.3-0ubuntu2
Unfortunately I did not find a snapshot thereafter either.
--
'qemu-img snapshot' crashed, corrupting disk image
Cannot reproduce this problem with a Lucid alpha3 guest running on a Lucid
alpha 3 host.
qemu-kvm Version: 0.12.3-0ubuntu2
--
qemu corrupts screen on resize
https://bugs.launchpad.net/bugs/426822
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This seems to be fixed on Lucid alpha 3:
$ qemu -cpu pentium lucid.qcow2
kvm_run: Exec format error
kvm_run returned -8
$ qemu -cpu 486 lucid.qcow2
kvm_run: Exec format error
kvm_run returned -8
$ qemu -cpu pentium -no-kvm lucid.qcow2
(runs, slowly)
--
qemu segfaults with a -cpu option
On Lucid Alpha3 I don't get console error messages, but a
error: unknown command 'terminal'.
unaligned pointer 0x8ecc0002
Aborted. Press any key to exit.
--
kvm with -vga std give error and do not works
https://bugs.launchpad.net/bugs/513273
You received this bug notification because you are a
I upgraded from Karmic to Lucid alpha 3 and cannot reproduce your
problem. virsh start works fine for my old VMs.
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bugs/512259
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
On Lucid alpha 3 an error is reported and kvm stops:
$ sudo kvm -net nic -net user,hostfwd=tcp:127.0.0.1:-:80 -net
user,hostfwd=tcp:127.0.0.1:-:22 -m 128 -smp 1 -drive file=disk0.qcow2kvm
-net nic -net user,hostfwd=tcp:127.0.0.1:-:80 -net
user,hostfwd=tcp:127.0.0.1:-:22 -m 128
According to the original bug reporter this problem has been resolved in
Lucid.
--
assertion failure when using i82551 network card emulation
https://bugs.launchpad.net/bugs/450309
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm
I'm pretty sure I waited for the front-end to be ready, e.g. euca-
describe-availability-zones verbose returns a good output. I attach the
registration log from the front-end.
On the node the authorized_keys file contain a good key for the
frontend. As user eucalyptus on the front-end I can do a
I tried the deregister and register but not change in the overall
situation.
For the logs on the node controller, I don't see nc.log:
ubu...@node01:/var/log/eucalyptus$ ls
axis2c.log euca_test_nc.log httpd-nc_error_log
--
[alpha3] NC fails to be detected.
Nothing of interest in there, I attach the two
** Attachment added: httpd-nc_error_log
http://launchpadlibrarian.net/39962164/httpd-nc_error_log
** Attachment added: euca_test_nc.log
http://launchpadlibrarian.net/39962165/euca_test_nc.log
--
[alpha3] NC fails to be detected.
After reinstallation nothing changes. I removed quiet and splash from the
kernel boot command line and see the following report:
init: eucalyptus-network (lo) main process (704) killed by TERM signal
--
[alpha3] NC fails to be detected.
https://bugs.launchpad.net/bugs/530091
You received this
1 - 100 of 117 matches
Mail list logo
