You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Chip Childers (JIRA)" <ji...@apache.org> on 2013/06/04 20:55:31 UTC

[jira] [Updated] (CLOUDSTACK-1187) Handle network creation failures when persistent is set to true

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

Chip Childers updated CLOUDSTACK-1187:
--------------------------------------

    Fix Version/s:     (was: 4.1.0)
                   4.2.0
    
> Handle network creation failures when persistent is set to true
> ---------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1187
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1187
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.1.0
>            Reporter: Sailaja Mada
>            Assignee: Likitha Shetty
>             Fix For: 4.2.0
>
>
> Steps:
> 1. Configured 4.1 dev environment with latest master code
> 2. Configured Advanced zone with xen 6.1 as hypervisor 
> 3. Create network offering with persistent option enabled 
> Case 1: Tried to create persistent network when system templates are not downloaded yet 
> Case 2:  When there are no public IP's available 
> Observation with above 2 failure cases to create network:
> 1. Network got created but it was in implementing state .  This can not be used and it does not allow to delete.
> 2. DB entry still persists so always this stale network will be shown in GUI. 
> So can we have a better way to handle network failures where persistent is set to true.

--
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