Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-5382

FIWARE.Request.Lab.Prague.Re-2: FIWARE Lab Problem creating Blueprint Instance

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Fix Version/s: 2021
        • Component/s: FIWARE-LAB-HELP
        • Labels:
          None

          Description

          Hi,
          yes I had testet it with a plain template but with one tier. But i got the same error.
          Now I have create a new template with 3 tiers, but i doesn't work also.
          My community accout is burkhard-krome cloud
          I'm in the Prague Node.
          Burkhard

          Original Message processed by David.fx12
          Re: [Fiware-lab-help] FIWARE Lab Problem creating Blueprint Instance (23-Nov-2015 10:40)
          From: Giuseppe Cossu
          To:GFG
          Cc:fiware-lab-help@lists.fiware.org

          Hi,
          is it related to this template or have you tried other templates with different settings?
          I need also to know the name of your community account and in which fiware-lab node are you working.

          Regards,
          Giuseppe

          On Mon, Nov 23, 2015 at 10:08 AM, GFG <info@gfg.net> wrote:

          Hi,
          I have a problem to deploy a Blueprint instance.
          I had create a Blueprint Template (Test01Template) which I clone from the cep at the Blueprint Template Catalog.
          I added some Software ( nodejs 0.9.0, git 1.7, mongodb 2.4.9 ).
          When I go to Actions -> Launch Template (I named it Test01Instance)
          In the Tab Blueprint Instances is my new Instance listed. But the status-column shows ERROR. In the console following error is described:
          Error: Infrastructure error Error interacting with OpenStack Error creating server: String index out of range: -10
          Burkhard Krome

          Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
          Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
          _______________________________________________
          Fiware-lab-help mailing list
          Fiware-lab-help@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-lab-help

          To: giuseppe.cossu@create-net.org
          Cc: fiware-lab-help@lists.fiware.org

          Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
          Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
          _______________________________________________
          Fiware-lab-help mailing list
          Fiware-lab-help@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-lab-help
          [Created via e-mail received from: GFG <info@gfg.net>]

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            gcossu Giuseppe Cossu added a comment -

            Hi,
            I've forwarded your request to the Prague node support.

            Regards,
            Giuseppe

            Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
            Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
            _______________________________________________
            Fiware-lab-help mailing list
            Fiware-lab-help@lists.fiware.org
            https://lists.fiware.org/listinfo/fiware-lab-help

            Show
            gcossu Giuseppe Cossu added a comment - Hi, I've forwarded your request to the Prague node support. Regards, Giuseppe Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one. _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-help
            Hide
            Permalink
            mev Manuel Escriche added a comment -

            Please, use the instructions at the link http://backlog.fiware.org/guide/tracker.html#email-issue to answer issues in the help desk. Thanks!!

            Show
            mev Manuel Escriche added a comment - Please, use the instructions at the link http://backlog.fiware.org/guide/tracker.html#email-issue to answer issues in the help desk. Thanks!!
            Hide
            Permalink
            alfopietro Pietropaolo Alfonso added a comment -

            Dear Prague team, any news about this ticket? Can you close it?

            Show
            alfopietro Pietropaolo Alfonso added a comment - Dear Prague team, any news about this ticket? Can you close it?
            Hide
            Permalink
            henar Henar Muñoz added a comment -

            Hi
            I was debugging, and I can see that I obtained a 404 error from Prague infrastructure. Item not found. Prague, could you check logs and tell me what it is missing? My tenant Id is 0000000000000000000000000000008.
            Thanks a lot,
            Henar

            Show
            henar Henar Muñoz added a comment - Hi I was debugging, and I can see that I obtained a 404 error from Prague infrastructure. Item not found. Prague, could you check logs and tell me what it is missing? My tenant Id is 0000000000000000000000000000008. Thanks a lot, Henar
            Hide
            Permalink
            prgsupportteam Prague Node Helpdesk added a comment -

            Hi,
            We tried to localize a cause of this error and we can state:

            There is nothing suspicious in internal logs of openstack. The error is probably related to default network, security group or keypairs. May be related to the fact that we in prague dont use neutron but nova-network.

            We also tried to run own clone of cep blueprint (under our own account) in Spain2 node and the error is looks identically. It looks more like a some problem with blueprint.

            Actually you can start VM from default images (not blueprint) and install necessary SW afterwards.

            Show
            prgsupportteam Prague Node Helpdesk added a comment - Hi, We tried to localize a cause of this error and we can state: There is nothing suspicious in internal logs of openstack. The error is probably related to default network, security group or keypairs. May be related to the fact that we in prague dont use neutron but nova-network. We also tried to run own clone of cep blueprint (under our own account) in Spain2 node and the error is looks identically. It looks more like a some problem with blueprint. Actually you can start VM from default images (not blueprint) and install necessary SW afterwards.

              People

              • Assignee:
                prgsupportteam Prague Node Helpdesk
                Reporter:
                fw.ext.user FW External User
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: