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

FIWARE.Request.Lab.Waterford.FI-Lab Assistance.

        Details

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

          Description

          Hi.

          I am getting an ERROR status when creating new instances in a region
          different from Spain. It appears with a BUILD status but then changes to
          ERROR. I have tried in a lot of different regions and I am only able to
          create new instances in Spain. Could you check if there is something wrong
          in my account.

          Thanks in advance,
          Alejandro Vera.

          _______________________________________________
          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: Alejandro Vera <alejandro.vera@centeropenmiddleware.com>]

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            fw.ext.user FW External User added a comment -

            Hi.

            I am having the problem in all the regions. I have been trying to launch
            instances for 3 hours in all the regions and I have only been able to
            create one a couple of times but then I was not able to assign it a
            floating ip...
            I have tried again with Waterford but I still have the same error.
            Inspecting the "detail" request with the developer tools of my browser I
            get the following in "fault":

            {"message":"NoValidHost","code":500,"created":"2015-02-04T12:30:47Z"}

            Regards,
            Alejandro Vera.

            Show
            fw.ext.user FW External User added a comment - Hi. I am having the problem in all the regions. I have been trying to launch instances for 3 hours in all the regions and I have only been able to create one a couple of times but then I was not able to assign it a floating ip... I have tried again with Waterford but I still have the same error. Inspecting the "detail" request with the developer tools of my browser I get the following in "fault": {"message":"NoValidHost","code":500,"created":"2015-02-04T12:30:47Z"} Regards, Alejandro Vera.
            Hide
            Permalink
            henar Henar Muñoz added a comment -

            Hi

            About Waterford region, I will send this ticket to Waterford support. About floating ip, you should provide more information, so that, we can send the information to the right administrator.
            Regards,
            Henar

            Show
            henar Henar Muñoz added a comment - Hi About Waterford region, I will send this ticket to Waterford support. About floating ip, you should provide more information, so that, we can send the information to the right administrator. Regards, Henar
            Hide
            Permalink
            fw.ext.user FW External User added a comment -

            Hi.

            An example of the floating ip errors is Berlin, where I have been able to
            create an instance (COMPydio: 4baff882-77f6-4b17-9cdb-a00c9f449763) and I
            have a floating ip 193.175.132.49 from the ext-net-public. When I try to
            associate them there is an error: undefined. Cause: 400 Error
            {"badRequest": {"message": "Error. Unable to associate floating ip",
            "code": 400}}

            Thanks for your help.

            Regards,
            Alejandro Vera.

            Show
            fw.ext.user FW External User added a comment - Hi. An example of the floating ip errors is Berlin, where I have been able to create an instance (COMPydio: 4baff882-77f6-4b17-9cdb-a00c9f449763) and I have a floating ip 193.175.132.49 from the ext-net-public. When I try to associate them there is an error: undefined. Cause: 400 Error {"badRequest": {"message": "Error. Unable to associate floating ip", "code": 400}} Thanks for your help. Regards, Alejandro Vera.
            Hide
            Permalink
            Tynan Waterford Node Helpdesk added a comment -

            Hi,

            All of our floating IP's have been assigned. The reason to the 500 Error on the Waterford node. ( the user will need a min of two IPs to get out of their tenant network. )
            If public IP addresses are freed up and become available only then can I help.

            Regards,
            Joe.

            Show
            Tynan Waterford Node Helpdesk added a comment - Hi, All of our floating IP's have been assigned. The reason to the 500 Error on the Waterford node. ( the user will need a min of two IPs to get out of their tenant network. ) If public IP addresses are freed up and become available only then can I help. Regards, Joe.

              People

              • Assignee:
                Tynan Waterford Node Helpdesk
                Reporter:
                fw.ext.user FW External User
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: