[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956865#comment-14956865
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8832:
--------------------------------------------

Github user nlivens commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/801#discussion_r41989738
  
    --- Diff: 
plugins/network-elements/nuage-vsp/src/com/cloud/network/resource/NuageVspResource.java
 ---
    @@ -424,9 +449,10 @@ private Answer executeRequest(ApplyAclRuleVspCommand 
cmd) {
         private Answer executeRequest(ShutDownVpcVspCommand cmd) {
             try {
                 isNuageVspElementLoaded();
    -            _nuageVspElementClient.shutDownVpc(cmd.getDomainUuid(), 
cmd.getVpcUuid());
    +            _nuageVspElementClient.shutdownVpc(cmd.getDomainUuid(), 
cmd.getVpcUuid(), cmd.getDomainTemplateName());
                 return new ShutDownVpcVspAnswer(cmd, true, "Shutdown VPC " + 
cmd.getVpcUuid());
             } catch (Exception e) {
    --- End diff --
    
    Our client is using internal exceptions, which are not available in ACS, 
and which translated to <code>Exception</code> before we return from the 
client. Therefore we need to catch on <code>Exception</code>


> Update Nuage VSP plugin to work with Nuage VSP release 3.2
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-8832
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.6.0
>            Reporter: Nick Livens
>            Assignee: Nick Livens
>         Attachments: nuageVspMarvinLogs.tar.gz
>
>
> Nuage VSP 3.2 is being released, we want to bring the plugin up to date for 
> this release



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

Reply via email to