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
Henar Muñoz
created issue -
PiraeusU Node Helpdesk
made changes -
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | Answered [ 10104 ] |
PiraeusU Node Helpdesk
made changes -
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Done [ 10000 ] |
Manuel Escriche
made changes -
Component/s | FIWARE-LAB-HELP [ 10279 ] |
Manuel Escriche
made changes -
Workflow | FW eRequest Workflow [ 29873 ] | FW extRequest Workflow-II [ 41133 ] |
Status | Done [ 10000 ] | Closed [ 6 ] |
Issue Type | eRequest [ 10101 ] | extRequest [ 10104 ] |
Backlog Manager
made changes -
Summary | I cannot associate a floating Ip to a VM | FIWARE.Request.Lab.I cannot associate a floating Ip to a VM |
Manuel Escriche
made changes -
HD-Node | PiraeusU [ 10920 ] |
Backlog Manager
made changes -
Summary | FIWARE.Request.Lab.I cannot associate a floating Ip to a VM | FIWARE.Request.Lab.PiraeusU.I cannot associate a floating Ip to a VM |
Fernando Lopez
made changes -
Fix Version/s | 2021 [ 12600 ] |
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
13h 40m | 1 | PiraeusU Node Helpdesk | 27/May/15 5:27 AM | |||||
|
45s | 1 | PiraeusU Node Helpdesk | 27/May/15 5:27 AM | |||||
|
230d 4h 43m | 1 | Manuel Escriche | 12/Jan/16 9:10 AM |
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