[Fiware-lab-help] Fwd: Failed to launch new instances

Federico Michele Facca federico.facca at create-net.org
Thu Jan 22 09:56:20 CET 2015


Hi Tero,
Stockholm support reads your reporting. So they will perform the needed
checks. Regarding DNS, I think this is the default behaviour when using
private networks: you need to define one yourself.

Best,
Federico

On Thu, Jan 22, 2015 at 6:15 AM, Tero Vuorela <tero.vuorela at iki.fi> wrote:

>  Hi Federico,
>
> Thank you for your guidance. I have managed to go forward but I also still
> face few problems. Here is what I have done using Stockhom region:
>
> I managed to associate floating IP and ssh connection worked fine. However
> the server couldn't connect Internet properly: host names were not
> resolved. It seemed that the server didn't get working DNS name servers via
> DHCP. After trying rebooting and some configuration changes I added public
> google DNS servers to subnet configuration. I wonder is this way to go and
> are there FIWare specific DNS servers that should be used, or is varying
> between regions?
>
> Anyway things looked fine, so I started to update packages using
> 'apt-get'. However during installing packages server froze and ssh
> connection died. After that I couldn't connect using ssh to the server,
> reboots didn't help. I get just 'no route to host' error while trying ssh
> connection. I tried redefining configurations, rebooting but nothing seemed
> to help.
>
> I have other user account for testing and I followed my own notes and
> managed to launch instance and associate floating IP. Ssh connection
> started working right away.
>
> Now I went back to the original account and deleted everything on
> Stockholm region: instances, networks, routers and released IPs. I
> recreated the setup again. The creation and IP association went fine, but
> still my ssh connection refuses to work: no route to host.
>
> So I'm in situation that I have two accounts and VM instances running on
> Stockholm region
>  - on one account everything is ok, ssh connection working (public IP
> 194.28.122.40). Updating packages using 'apt-get' on this server went fine.
>  - on other account the server is running but I can't connect using ssh
> (public IP almost same 194.28.122.53). No route to host.
>
> So right now I have server that I can continue to use for my work. However
> I would like to help you to troubleshoot situation because right now it
> feels that the setup is unrealiable (I don't know is it because of FI-Lab
> in general or related to Stockholm region).
>
> There is web based VNC connection on Connection tab of instances. On some
> regions it really shows console screen but on Stockholm region 'View
> Display' gives  Corrupted Content Error. Should this 'View Display'
> generally work? If yes, then what root password to use? There is 'Change
> Password' for instances but I haven't seen it working.
>
>
> Regards,
> Tero Vuorela
>
>
>
> On Mon, Jan 19, 2015, at 06:25 PM, Federico Michele Facca wrote:
>
> Hi Tero,
> I got the message from sys admins that a set of public IPs has be been
> made available to developers. So you should be able to attach the gateway
> and self-assign a floating ip. If you still have problems, i will put you
> directly in contact with them.
>
> Best,
> Federico
>
> On Mon, Jan 19, 2015 at 10:32 AM, Federico Michele Facca <
> federico.facca at create-net.org> wrote:
>
> Hi Tero,
> I assigned your ticket to stockholm infrastructure, they will assign you a
> floating ip.
>
>
> Federico
>
>
> On Mon, Jan 19, 2015 at 6:10 AM, Tero Vuorela <tero.vuorela at iki.fi> wrote:
>
>
> Hi,
>
> Thanks for help. I have now successfully launched an VM using Stockholm
> node. I have created a private network and a router according to
> instructions. Now only public floating IP is missing so that I could start
> working with the server.
>
> I'm able to create floating IP from the pool XIFIfederatedACREO, but based
> on its name it is not probably what is needed. Also if I try to associate
> the IP to the created VM I get an error: {"badRequest": {"message": "Error.
> Unable to associate floating ip", "code": 400}}.
>
> Creating from the pool XIFIpublicACREO fails with {"computeFault":
> {"message": "The server has either erred or is incapable of performing the
> requested operation.", "code": 500}} but this is seems to be because public
> IP need to be requested separately?
>
> What information you need for requesting public floating IP for Stockholm
> node?
> Network is
> GBerryNetwork
> <https://cloud.lab.fiware.org/#neutron/networks/9550acfc-e9e3-4b2b-9646-4d604582493b>
> *Subnet1* 192.168.100.0/24
>
>    - *Name:* (9550acfc-e9e3-4b2b-9646-4d604582493b)
>    - *ID:* 9550acfc-e9e3-4b2b-9646-4d604582493b
>
>
> Router
>
>    - *Name:* GBerryRouter
>    - *ID:* f5fc79d7-8d9c-4d54-8e4b-357b5841a0da
>    - *Status:* ACTIVE
>    - *External Gateway Information: *
>    - *Connected External Network:* XIFIpublicACREO
>
>
> VM instance
>
>    - *Name: * GBerryStockholmUbuntu14Large
>    - *ID: * e5a9483f-a4ba-4ddc-ac8f-2b240172ea94
>    - *Status: * ACTIVE
>
>
>
> Regards,
> Tero
>
> On Thu, Jan 15, 2015, at 06:46 PM, Federico Michele Facca wrote:
>
> Dear Tero,
> regarding Prague, I am not sure what is the issue you are experiencing.
> May it be you selected a flavour that is too small?
> In budapest, I experienced your issue as well, thus I suspect they are
> having problem at the moment.
>
> Anyhow, I tested both the nodes closest to you: Karlskrona and Stockholm.
> No issue to launch vms. You will need anyhow to create your own private
> network and request for a floating IP to the local sys admin to access the
> vm via public IP. (this last step need to be handled manually
> unfortunately).
>
> to try follow this guide:
>
> http://stackoverflow.com/questions/27543127/deploy-vm-in-fiware-lab-nodes-with-neutron
>
> except step 6 and 9. if you confirm me that you are able on one of the two
> nodes to launch vms, I will then ask the local sys admin to assign you a
> floating ip.
>
> Best,
> Federico
>
>
> On Thu, Jan 15, 2015 at 6:40 AM, Tero Vuorela <tero.vuorela at iki.fi> wrote:
>
>
> Hi,
>
> Thank you for your answer. If this is not a general problem, is there
> something I could do to help you to troubleshoot situation?
>
> I guess this should not be an issue of used browser. I'm using Firefox.
>
> Quickly testingI wouldn't expect this to be problem of a specific image. I
> have mainly tried Ubuntu 14.04 images but also tried CentOS and other ready
> made images.
>
> I have experimented many functions in FI-Lab portal, so I thought maybe I
> have managed to take my account is some unknown state and that might cause
> problems for launching instances. So I created a new account (
> theros at iki.fi).
>
> By the way I wanted to check if a second account is according to terms and
> conditions, but on sign up page the link
>
> http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FI-LAB_Terms_and_Conditions
> says
> FI-WARE Forge Could Not Connect to Database:
> and the link in a confirmation email
> http://wiki.fiware.org/FI-LAB_Terms_and_Conditions
> says
> PAGE NOT FOUND <https://forge.fi-ware.org/>
>
> With the new account I just selected Budapest: Creating publicRange IP
> failed
> {"computeFault": {"message": "The server has either erred or is incapable
> of performing the requested operation.", "code": 500}}
>
> but mdvpnRange IP creation was ok, although I wasn't able to associate it
> to successfully launched image.
>  {"badRequest": {"message": "Error. Unable to associate floating ip",
> "code": 400}}
>
> Based on floating IP name, mdvpnRange might not even be correct type of
> floating IP to get ssh access over public internet. Floating IP pools vary
> between regions, I haven't seen any instructions what should be selected
> although I can assume something based on a IP pool name.
>
> With the new account I also tried to launch instance on Prague region, but
> like before it started spawning and resulted soon to ERROR. So I don't see
> differences between accounts.
>
> I'm not in urgent hurry but I would like to having working setup as I'm
> right now starting to work with my project utilizing FIWare generic
> enablers. Please advice, if there is something I can do for helping
> troubleshooting.
>
>
> Regards,
> Tero Vuorela
>
>
>
>
>
> On Wed, Jan 14, 2015, at 10:52 AM, MIGUEL CARRILLO PACHECO wrote:
>
> Hi,
>
> Sorry to hear that this is causing so much trouble. Some nodes assign IP
> addresses upon request. Let us check if the Prague node has free IP
> addresses first. Each node has a separate 2nd level team locally, I'll
> contact the Czech one right away.
>
> If they fail to provide a good answer soon (hopefully not), then we can
> move to the Budapest team.
>
> In response to your general question, the answer is that we are not aware
> of a general problem.
>
> Best regards,
>
> Miguel
> El 13/01/2015 a las 20:57, Tero Vuorela escribió:
>
> 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 at iki.fi> <tero.vuorela at iki.fi>
> To: fiware-lab-help at 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
>
>
>
>
> _______________________________________________
> Fiware-lab-help mailing listFiware-lab-help at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help
>
>
>
> --
>
> Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com
>
> ----------------------------------------------------------------------
>      _/          _/_/                     Miguel Carrillo Pacheco
>     _/   _/     _/  _/   Telefónica       Distrito Telefónica
>    _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 9
>   _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N
>  _/          _/_/                         28050 Madrid (Spain)
>                                           Tel:  (+34) 91 483 26 77
>
>                          e-mail: miguel.carrillopacheco at telefonica.com
>
> Follow FIWARE on the net
>
> 	Website:  http://www.fiware.org
> 	Facebook: https://www.facebook.com/eu.fiware
> 	Twitter:  http://twitter.com/Fiware
> 	LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
> ----------------------------------------------------------------------
>
>
> ------------------------------
>
>  Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
>  The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
>
>  Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> destinatário, pode conter informação privilegiada ou confidencial e é para
> uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o
> destinatário indicado, fica notificado de que a leitura, utilização,
> divulgação e/ou cópia sem autorização pode estar proibida em virtude da
> legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos
> o comunique imediatamente por esta mesma via e proceda a sua destruição
>
>
>  --
> Tero Vuorela
> tero.vuorela at iki.fi
>
>
>
> _______________________________________________
> Fiware-lab-help mailing list
> Fiware-lab-help at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-lab-help
>
>
>
>
>
> --
> --
> Future Internet is closer than you think!
> http://www.fiware.org
>
> Official Mirantis partner for OpenStack Training
> https://www.create-net.org/community/openstack-training
>
> --
> Dr. Federico M. Facca
>
> CREATE-NET
> Via alla Cascata 56/D
> 38123 Povo Trento (Italy)
>
> P  +39 0461 408400 (1669)
> M +39 334 6049758
> E  federico.facca at create-net.org
> T @chicco785
> W  www.create-net.org
>
>
>  --
> Tero Vuorela
> tero.vuorela at iki.fi
>
>
>
>
>
>
> --
> --
> Future Internet is closer than you think!
> http://www.fiware.org
>
> Official Mirantis partner for OpenStack Training
> https://www.create-net.org/community/openstack-training
>
> --
> Dr. Federico M. Facca
>
> CREATE-NET
> Via alla Cascata 56/D
> 38123 Povo Trento (Italy)
>
> P  +39 0461 408400 (1669)
> M +39 334 6049758
> E  federico.facca at create-net.org
> T @chicco785
> W  www.create-net.org
>
>
>
>
> --
> --
> Future Internet is closer than you think!
> http://www.fiware.org
>
> Official Mirantis partner for OpenStack Training
> https://www.create-net.org/community/openstack-training
>
> --
> Dr. Federico M. Facca
>
> CREATE-NET
> Via alla Cascata 56/D
> 38123 Povo Trento (Italy)
>
> P  +39 0461 408400 (1669)
> M +39 334 6049758
> E  federico.facca at create-net.org
> T @chicco785
> W  www.create-net.org
>
>
> --
> Tero Vuorela
> tero.vuorela at iki.fi
>
>
>



-- 
--
Future Internet is closer than you think!
http://www.fiware.org

Official Mirantis partner for OpenStack Training
https://www.create-net.org/community/openstack-training

-- 
Dr. Federico M. Facca

CREATE-NET
Via alla Cascata 56/D
38123 Povo Trento (Italy)

P  +39 0461 408400 (2471)
M +39 334 6049758
E  federico.facca at create-net.org
T @chicco785
W  www.create-net.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150122/9f66a42b/attachment.html>


More information about the Fiware-lab-help mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy