[jira] [Commented] (CLOUDSTACK-5964) [Automation] Assigning virtual machine (belonging to persistent network) to other account, creates a non persistent network instead of persistent one

["Ram Ganesh (JIRA)" <ji...@apache.org>]

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

Ram Ganesh commented on CLOUDSTACK-5964:
----------------------------------------

Whether a network is persistent or not is a property of  network and NOT of a VM isn't? So above use is valid - VM should not dictate if the network should be persistent or not.

I am resolving this bug as as-design. Please re-open if you disagree and you have a use case 

> [Automation] Assigning virtual machine (belonging to persistent network) to other account, creates a non persistent network instead of persistent one
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5964
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5964
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.4.0
>         Environment: Observed on VMware yet
>            Reporter: Gaurav Aradhye
>              Labels: automation
>             Fix For: 4.4.0
>
>
> Steps to reproduce:
> 1. Create an account (account-1), create a persistent network in it
> 2. Deploy VM in this persistent network
> 3. Create another account (account-2) and assign the VM to this account
> 4. Check the network created in account-2
> 5. The network created should be persistent, but instead non persistent network is created
> I have not attached any logs as there are no exceptions or anything to debug.
> Please let me know in case you need some specific data from logs.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)