[jira] [Closed] (CLOUDSTACK-3407) network remains in 'allocated' if nic is added to it as first action

["Marcus Sorensen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Sorensen closed CLOUDSTACK-3407.
---------------------------------------

    Resolution: Fixed
      Assignee: Marcus Sorensen

This is the 4.1 version of CLOUDSTACK-2083. Applied to 4.1.
                
> network remains in 'allocated' if nic is added to it as first action
> --------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3407
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3407
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.1.0
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: 4.1.1
>
>
> 1. Create a VPC
> 2. Create a network
> 3. Create a VM
> 4. Create a second netowrk
> 5. Add nic to vm on second network
> result:  Second network remains allocated, rather than implemented. Normally when the first vm is launched the network is provisioned, this isn't happening if a nic is added to a running VM as the first action on the network. This seems like there would be a simple fix.
> Not sure if this applies to 4.2.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira