nvazquez opened a new pull request #3018: Prevent error on GroupAnswers on VR creation URL: https://github.com/apache/cloudstack/pull/3018 ## Description On VR creation it has been noticed that management server receives these answers: ```` { Ans: , MgmtId: 7206518937063, via: 11, Ver: v1, Flags: 10, [{"com.cloud.agent.api.routing.GroupAnswer":{"results":["null - success: Creating file in VR, with ip: 169.254.3.212, file: vm_password.json.2b0e06a0-821f-41f1-bf8f-b9805f490a6c","null - success: Error: inet prefix is expected rather than \"table\".\nError: inet address is expected rather than \"table\".\n"],"result":true,"wait":0}},{"com.cloud.agent.api.routing.GroupAnswer":{"results":["null - success: Creating file in VR, with ip: 169.254.3.212, file: vm_metadata.json.01da0832-2dd7-451b-a526-1de81d737a80","null - success: Error: inet prefix is expected rather than \"table\".\nError: inet address is expected rather than \"table\".\n"],"result":true,"wait":0}}] } ```` This has been originated by empty parameters on VR commands: (cloud.log) ```` 2018-11-05 16:50:59,260 CsHelper.py execute:188 Executing: ip route show default via table Table_eth0 proto static Error: inet prefix is expected rather than "table" 2018-11-05 16:50:59,269 CsHelper.py execute:188 Executing: ip route add default via table Table_eth0 proto static Error: inet address is expected rather than "table" ```` ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [x] Bug fix (non-breaking change which fixes an issue) - [ ] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) ## How Has This Been Tested? Deploy VM on Isolated or Shared network - VR created
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
