Hello,

I have got answer to my earlier post and I was instructed to use either
Budapest or Prague regions. I tested those:

• Budapest: Instance creation fails here too like I have described
  below. Deployment starts but ends to simple ERROR. No additional
  information.

• Prague: I managed successfully launch instance but I'm unable to
  allocate IP. There I get reasonable error message
  Error allocating IP address. Cause: 404 Error
  {"itemNotFound": {"message": "NoMoreFloatingIps: Zero floating ips
  available.", "code": 404}}
  How ever when "Allocate Floating IP" dialog is open quota said that
  there is one available.

I systematically went through all regions and (just for me?) all but
Poznan failed in away or another: either VM launching results to error
or floating IPs can't be assigned. On Poznan region I managed to connect
a launched VM with ssh.

I still wonder is this a general error situation, or is it just me who
is experiencing these problems.

Regards
Tero Vuorela

----- Original message -----
From: Tero Vuorela <tero.vuorela@iki.fi>
To: fiware-lab-help@lists.fi-ware.org
Subject: Failed to launch new instances
Date: Sat, 10 Jan 2015 10:30:43 +0200

Hi,

I trying to launch new instances in Fi-Lab but for some reason launching
fails every time and instance gets into error state. See attached
screenshot. I can't find any additional information for the error.

I tried different regions and different instances, but a result is same:
ERROR

I originally had a test instance running on Spain region, that was
launched in October but I deleted it as I couldn't anymore find keypair,
and understood that you can't associate new keypairs to existing
instance.

Is there a general problem in Fi-Lab, or am I just missing some step?

Regards,
Tero Vuorela

–
Tero Vuorela
tero.vuorela@iki.fi

–
Tero Vuorela
tero.vuorela@iki.fi

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

[Created via e-mail received from: Tero Vuorela <tero.vuorela@iki.fi>]