Diogo Monteiro created CLOUDSTACK-8192:
------------------------------------------

             Summary: Wrong ID being returned in the createEgressFirewallRule 
end-point response
                 Key: CLOUDSTACK-8192
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8192
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
         Environment: Issue was found on cloudstack version 4.2.1
            Reporter: Diogo Monteiro
            Priority: Blocker


Instead of returning the rule UUID, the endpoint is returning the database 
primary key. This causes an issue since most third party applications expect 
async endpoints to return the asyncJobId and the resource UUID as part of the 
response

Steps to reproduce:

#1 Make a request to the createEgressFirewallRule endPoint
http://cs42.dev.cloud:8096?action=ALLOW&apiKey=j-DKJIkURhA2G4H0vg3Tba-a75SasolsL8sRZbEAxKlq-AihyVElV7dhaAMjf-jOTOwzu8zEoKb-2krJjr8r3Q&cidrlist=0.0.0.0%2F0&command=createEgressFirewallRule&endport=81&networkid=e5a1cb87-b6da-4e41-b6c2-2bc686713d0f&number=1003&protocol=TCP&response=json&startport=81&traffictype=INGRESS&signature=aT8dtBE%2FTb34205sfKHckXXPGcQ%3D

Results
Response object return primary key instead of UUID:
"createegressfirewallruleresponse": {
      "id": "78",
      "jobid": "05626600-fb64-4558-b5ce-675294e9f48f"
    }

Expected Results:
createegressfirewallruleresponse object should contain the rule UUID



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to