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

FIWARE.Request.Lab.PiraeusU.I cannot associate a floating Ip to a VM

        Details

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

          Description

          I obtain the error
          {"badRequest": {"message": "Error. Unable to associate floating ip", "code": 400}}

          The ip is 83.212.237.229
          And the VM is Name: asdfasd-asdf-1-000081
          ID: 22a8009e-e302-4ad1-8baa-7182b4876675

          Regards,
          Henar

            Activity

            Hide
            Permalink
            UPRC PiraeusU Node Helpdesk added a comment -

            Dear Henar,

            we investigate the issue and we conclude that this sometimes happens due to a very strange error that refers to a non supported type of string/character that is part of the request. This character is the symbol '+', but unfortunately we did not find how it was added on the request. However, after repetitive manual test as well as by taking the latest results of the automate sanity test we found that the problem did not appeared again. In addition we check you instance into our OS (PiraeusU) cloud infra and seems that you instance has an associated md-vpn ip (10.0.208.96).
            Consequently, we could considered the current issue as closed/done.
            Please feel free to contact us.

            Best Regards,
            Dimitris Kelaidonis, on behalf of PiraeusU node tech team

            Show
            UPRC PiraeusU Node Helpdesk added a comment - Dear Henar, we investigate the issue and we conclude that this sometimes happens due to a very strange error that refers to a non supported type of string/character that is part of the request. This character is the symbol '+', but unfortunately we did not find how it was added on the request. However, after repetitive manual test as well as by taking the latest results of the automate sanity test we found that the problem did not appeared again. In addition we check you instance into our OS (PiraeusU) cloud infra and seems that you instance has an associated md-vpn ip (10.0.208.96). Consequently, we could considered the current issue as closed/done. Please feel free to contact us. Best Regards, Dimitris Kelaidonis, on behalf of PiraeusU node tech team

              People

              • Assignee:
                UPRC PiraeusU Node Helpdesk
                Reporter:
                henar Henar Muñoz
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: