Public bug reported:
One cloud is already running. When installing a new cloud in the same
subnet, auto registration of nodes to the second cloud does not seem to
work.
>From the CLC registration.log:
2010-04-30 10:41:13-04:00 | 3882 -> Calling node rockstars-cluster node
10.153.108.113
2010-04-
After stopping the other cloud and reinstalling it worked.
--
NC not available when auto registrating with second cloud present
https://bugs.launchpad.net/bugs/572388
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
-
Public bug reported:
The 172.19.1.2 IP address was assigned twice in this cloud:
$ euca-describe-instances
RESERVATION r-4AAA0905 admin default
INSTANCEi-42F507EC emi-6E2F1366172.19.1.2 172.19.1.2
running admin 0 m1.small2010-05-03T10
This seems to have happened while dnsmasq was running on an instance -
the instance got the ip from itself. After disabling dhcp for dnsmasq on
another trial instance, the problem could no longer be reproduced.
--
private ip address assigned twice
https://bugs.launchpad.net/bugs/574366
You receiv
On Fri, 2010-05-07 at 14:35 +, Jason Rogers wrote:
...
> I had a guest vm running on a eucalyptus cloud using virtio for disk and
> network I/O. I also had an ssh session on the guest vm. When I attach a
> volume to the instance using euca-attach-volume I lose network
> connectivity to the gues
The first existing cloud was using the simple topology: one front-end,
one node controller. The cloud we installed first was made up of 3
machines: 1 CLC+Walrus, 1 CC+SC, 2 NC.
After installing the second cloud, both clouds had two clusters
registered against it. However, the output of euca-descri
On Wed, 2010-05-19 at 11:35 +, brian mullan wrote:
> Are both "clouds" on the same network segment?
Yes.
> If so is there any chance that the NC of the 2nd cloud confused as to which
> CLC it belongs to?
Quite possible.
> Is DHCP configured in both CLC's?
It's not configured on either on
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:
$ su
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
https://bu
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 ar
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-598F062A1
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:
[We
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 2011][0
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 w
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 ] RunI
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 S
>From time to time I see these timeouts, could they be related?
4 0 8
path=/services/Eucalyptus/?AWSAccessKeyId=WKy3rMzOWPouVOxK1p3Ar1C2uRBwa2FBXnCw&A
ction=TerminateInstances&InstanceId.1=i-47F10968&InstanceId.2=i-4D930877&Instanc
eId.3=i-2BFF05A8&InstanceId.4=i-48E108C9&InstanceId.5=i-5
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 eucalyptus
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 sta
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.
https://bugs.launchpa
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
** 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 notific
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 ma
** 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 notification
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 th
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.
https://bu
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 (2.0.1+bzr
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.
https://bugs.la
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 Ubunt
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.
https:/
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.
h
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.
https://bugs.
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 notific
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.
https://bugs.launchpa
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 so
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 to
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:
O
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 not
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 e
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 certa
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 U
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
Yo
*** 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 notif
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 b9
>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 not
>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
https://bugs.launchpad.net/bugs/4
The relevant code seems to be in 'EucalyptusWebInterface.java. When the
IP detection does not work (it will most likely fail for any private UEC
install), ip is set to:
String in = cloudInfo.getInternalHostPort();
After looking at CloudInfoWeb.java I wonder if servicePath
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 172.24.
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 $(euca-
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
h
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
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 rep
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 2010][001
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 su
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
/etc/eucalyptus/
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
https://bugs.l
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 subscrib
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
htt
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 m
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
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 p
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.
https://bugs.launchpad.net/bugs/53009
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.
https://
I confirm that on my cloud there is an eucalyptus-nc.conf on the node and it
reads
CC_NAME="torstentest"
I will reinstall the node controller next and see if the problem
persists.
--
[alpha3] NC fails to be detected.
https://bugs.launchpad.net/bugs/530091
You received this bug notification beca
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 bu
On Wed, 2010-03-03 at 09:48 +, Thierry Carrez wrote:
> Looking at the authorized_keys, might be a node re-registration issue.
> Did you register the same Node IP with the CC in the past ?
Yes, it was registered before.
> When you
> deregistered/registered manually the node, did you get any
On a fresh install of front-end and node controller the cloud works as
expected:
ubu...@frontend:/var/log/eucalyptus$ euca-describe-availability-zones verbose
AVAILABILITYZONEtorsten 192.168.1.103
AVAILABILITYZONE|- vm types free / max cpu ram disk
AVAILABILITYZONE
Having the option to host a complete UEC on one machine is also relevant
for training. Right now we fall back to one UEC per classroom due to the
two machine requirement, or at most students working in pairs.
--
After all-in-one setup node-cert.pem and node-pk.pem not found
https://bugs.launchpad
The bug also exists in Lucid, libvirt 0.7.5-5ubuntu9.
--
disappears after adding
https://bugs.launchpad.net/bugs/531741
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-
I tried to reproduce your kernel oops problem with the lucid alpha 3
server CD, but no kernel oops was given. Can you reproduce the error on
a different hardware?
--
daily server ISO install fails with a kernel OOPS in KVM
https://bugs.launchpad.net/bugs/531455
You received this bug notification
*** This bug is a duplicate of bug 531823 ***
https://bugs.launchpad.net/bugs/531823
It's a 32bit system, maybe that's the key difference?
> a) uname -a
spind...@spitfire:~/t$ uname -a
Linux spitfire 2.6.32-15-generic #22-Ubuntu SMP Tue Mar 2 02:24:17 UTC
2010 i686 GNU/Linux
> b) cat /proc
The bios files are missing from the package, instead there is still a
link pointing nowhere:
lrwxrwxrwx 1 root root 22 2010-03-05 08:26 vgabios.bin
-> ../vgabios/vgabios.bin
lrwxrwxrwx 1 root root 29 2010-03-05 08:26 vgabios-cirrus.bin
-> ../vgabios/vgabios.cirrus.bin
When the two links a
I just tried 0.12.3-0ubuntu5~ppa2 and I don't get any errors when launching
$ kvm -vga std -hda ./lucid.qcow2
--
kvm with -vga std is broken since karmic
https://bugs.launchpad.net/bugs/513273
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed t
On Wed, 2010-03-17 at 13:32 +, Jean-Pierre Dion wrote:
...
> 2)
> euca-upload-bundle -b kernel_bucket -m
> /tmp/vmlinuz-2.6.31-14-server.manifest.xml
...
> 3)
> euca-register kernel_buckets/vmlinuz-2.6.31-14-server.manifest.xml
Just to make sure that there is no typing mistake: the euca-regi
On Lucid, I don't get the Volume: Error communicating with Storage
Controller: CreateStorageVolume:Internal Error. error anymore. However,
not all volume groups are deleted:
$ sudo lvscan
ACTIVE'/dev/vg-wsdyiQ../lv-K0hXfA..' [1.00 GiB] inherit
$ sudo vgscan
Reading all physical v
Does it work without the -P 1 option?
--
qemu-kvm-0.12.3+noroms-0ubuntu2: qemu-nbd: error while reading
https://bugs.launchpad.net/bugs/546997
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mai
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], re
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], re
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 settin
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 lo
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 '_eucalyptus
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 eucalyptus
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: New
Public bug reported:
Build Version/Date: 1.6~bzr931-0ubuntu7
Environment used for testing: Ubuntu 9.10
Summary: The official UEC image fails to boot
Steps to Reproduce: Download
http://uec-images.ubuntu.com/releases/karmic/release/ubuntu-9.10-uec-amd64.tar.gz
U
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, wh
On Fri, 2009-10-30 at 10:07 +, Thierry Carrez wrote:
> Boots for me... Is it something you can reproduce every time ?
Yes, 4 out of 4 times. Can repeat it more often if needed.
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification becau
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
1 - 100 of 128 matches
Mail list logo
