coverity: bring down all high impact issue in upgrade code, so we can trigger on this while reviewing#604
Conversation
not strictly necessary in all but one case. done consequently.
|
cloudstack-pull-rats #89 SUCCESS |
|
cloudstack-pull-requests #787 SUCCESS |
and of course have them autoclosed
|
cloudstack-pull-rats #90 SUCCESS |
|
cloudstack-pull-requests #788 SUCCESS |
|
cloudstack-pull-analysis #22 ABORTED |
|
cloudstack-pull-analysis #23 SUCCESS |
|
cloudstack-pull-rats #136 SUCCESS |
|
cloudstack-pull-rats #137 SUCCESS |
|
cloudstack-pull-requests #834 SUCCESS |
|
cloudstack-pull-rats #138 SUCCESS |
|
cloudstack-pull-requests #835 SUCCESS |
|
cloudstack-pull-requests #836 SUCCESS |
|
cloudstack-pull-analysis #69 SUCCESS |
|
cloudstack-pull-analysis #70 SUCCESS |
|
cloudstack-pull-analysis #71 ABORTED |
|
LGTM 👍 |
|
LGTM |
* pr/604: coverity 1116563: resource count leak for accounts coverity 1116562: resource count resource leak coverity 1116612: update network cidrs firewall rules and acls coverity 1116610: upgrade cluster overprovisioning details coverity 1212194: reuse of prepared statements in try-block and of course have them autoclosed coverity 1225199: vmware dc upgrade coverity 1288575: replace all close with try-with-resource not strictly necessary in all but one case. done consequently. Signed-off-by: Daan Hoogland <daan@onecht.net>
* Removing sshKeyEnabled from template details * Hide cancel while deploying a vm * Disabling rather than showing cancel * Setting custom offerings to zero Fixes #604 Also : Hide cance button while deploying a vm Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
Assorted try-with-resource solutions to resource leaks.