Reinstalling fixes the issue on Maverick, but not fully tested on 11.04,
which could be a different issue.
--
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/765275
Title:
metadata s
As far as the new package containing the eucalyptus-interface jar file,
this is verified, and also fixes this escalation bug (package respin).
--
Missing jar file when Walrus/S3 runs on different host than CLC
https://bugs.launchpad.net/bugs/516083
You received this bug notification because you a
Agreed for Karmic.
It was mainly filed to make sure we test the most common and rapid way
to 'try' UEC which is to download and launch the 'default' image from
the store, and run it in the default instance size.
Is 192 meg a requisite for current uec lucid images?
--
default karmic image from im
Indeed, this solves it.
Thank you very much.
--
Cannot remove UEC/Eucalyptus users from webUI
https://bugs.launchpad.net/bugs/532700
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing lis
Public bug reported:
When creating users in the WebUI, there is no way to remove those users.
Only an edit button, but i cluld not find any way to deactivate or remove an
user.
Reproducable: Always
Steps:
Install UEC, connect to the web management interface (https:/:8443/) and
create many us
Ok, Verified and confirmed fixing.
I effectively get the right hostname without even a reboot.
Thanks !!
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are
Mathias Gug wrote:
> On Wed, Mar 03, 2010 at 11:45:13AM -0000, Boris Devouge wrote:
>> euca-run-instances emi-DFE5107D is the command line, after sourcing the
>> .euca/eucarc file.
>>
>
> Could add the command line used to register the image (emi-DFE5107D)?
This the
euca-run-instances emi-DFE5107D is the command line, after sourcing the
.euca/eucarc file.
The entity testing is only plainly following the docs there:
https://help.ubuntu.com/community/UEC/CDInstall
(Specifically Chapter 7)
apart that he omitted the -t c1.medium (which, funnily, does not run
Public bug reported:
This bug does not present a good initial experience to UEC new commers:
- When running the first instance, downloading the default Ubuntu 9.10
image from the Image Proxy, and try to simply launch it with all default
settings, fails to run the instance.
It seems the disk rese
Thanks Dustin. I hope to be able to get hardware for a Lucid cloud soon,
in the meantime i have not reproduced it yet, but i have verified as you
have that eucalyptus-interface-1.6.2.jar is indeed packaged in
eucalyptus-java-common_1.6.2.
As for Karmic, this is only about repackaging eucalyptus-ja
I did not thought the 'do-release-upgrade -d' method worked until we
release Lucid, or does it? Do you think it could have avoided the
breakage?
--
UEC upgrade from 9.10 karmic to Lucid fails
https://bugs.launchpad.net/bugs/519513
You received this bug notification because you are a member of Ubu
As additional comment, we understand Lucid is moving target, so the
importance of this bug should be well diminished as the upgrade will
need retesting with final lucid release.
--
UEC upgrade from 9.10 karmic to Lucid fails
https://bugs.launchpad.net/bugs/519513
You received this bug notificatio
Version info (after upgrade)
=
ii eucalyptus-cc1.6~bzr931-0ubuntu7.4
ii eucalyptus-cloud 1.6~bzr931-0ubuntu7.4
ii eucalyptus-common 1.6~bzr931-0ubuntu7.4
** Attachment added: "euca-debug.log"
http://launchpadlibrarian.net/38944263/euca-debug.log
--
UEC upgrade from 9.10 karmic to Lucid fails
https://bugs.launchpad.net/bugs/519513
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptu
Public bug reported:
Started with a 9.10 karmic fully updated as of yesterday UEC working
install, with one CLC/CC/SC and 2 NCs.
I proceed as follow:
- ssh in the NCs and stopped eucalyptus related services.
- ssh in the CLC and did the same
- updated my sources.list to lucid on all machines
Dustin,
Which version of UEC are you using? Not managed to get internal DNS
working here (up2date 9.10 UEC). Cheers.
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification beca
To be clear, i understand Eucalytus has a mapping as described in the
url Dan Nurmi provided, but i am trying to understand if it is the job
of UEC to assign a proper hostname to its instances (even when DNS is
missing), or if it sole responsibility is to launch the instances, even
if they all end
Thanks for all comment and explanations for the DNS services of
eucalyptus, however it is not accepted/possible in all cases, and not
the whole issue.
There is still an issue where we do not get an full IP attributed as a
hostname (which would help already assuming the uniqueness of hostnames
and
Sorry, this is fully updated Ubuntu 9.10 amd64 as of 01 Feb 2010.
--
Missing jar file when Walrus/S3 runs on different host than CLC
https://bugs.launchpad.net/bugs/516083
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubunt
Public bug reported:
Please see initial issue reported here:
http://open.eucalyptus.com/forum/walrus-configuration-failed-contact-
server
When running Walrus/S3 services of a different machine than the Cloud
controller (CLC), we are missing some jar files. We seems to assume that the
Walrus/S
This also badly breaks JBoss. I am not sure this is specific to Jboss,
as other java app servers will also most likely grab the wrong hostname.
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data
https://bugs.launchpad.net/bugs/475354
You received this bu
I am affected by this and have a 50 % failure rate (or success rate) ar
running images. One out of 2 of my launched instances from my 'custom'
image exhibits the same issue.
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification because you a
ubu...@172:~$ cat /etc/ec2-init/templates/hosts.tmpl
127.0.0.1 localhost
127.0.1.1 ubuntu
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
ubu...@
As suggested, tried editing /etc/ec2-init/templates/hosts.tmpl and
replacing the $hostname var with a fixed value (ubuntu), rebundling and
restarted the instance still landed me in a shell: ubu...@172
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data
ht
My experience on fully updated karmic amd64 kvm host:
- an ubuntu 8.04 LTS i386 guest crashes constantly (VM simply goes *poof* and
disappears after 5 to 10 minutes uptime)
- 9.10 amd64 guest lives
Now what is interesting relating to the 'acpi' suggested cause is:
- All 2 guests have defined i
25 matches
Mail list logo
