[
https://issues.apache.org/jira/browse/CLOUDSTACK-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677965#comment-13677965
]
Likitha Shetty commented on CLOUDSTACK-1187:
--------------------------------------------
Case 1: Tried to create persistent network when system templates are not
downloaded yet
Output - GET
command=createNetwork&response=json&sessionkey=LOSMotghR3SEs4ZKDHlDfqRibpI%3D&zoneId=6b071160-8010-4f02-b20e-12991f142132&name=p2&displayText=p2&networkOfferingId=48ab6777-6f26-4e8e-88eb-0bbaf0200949&_=1370602567861
533 Unable to create a deployment for VM[DomainRouter|r-5-VM]
Case 2: When there are no public IP's available
Output - GET
command=createNetwork&response=json&sessionkey=xWfuGJe%2BIuLP4NYwjI8alejneXE%3D&zoneId=22714988-1902-48a6-8ef4-233c95c44778&name=persistent&displayText=persistent&networkOfferingId=6b1be7d0-09bc-4533-9fce-a09ce1edfbbd&_=1370596277402
533 Insufficient address capacity
In both the above cases the network was in 'Allocated' state. This is the
desired state because the network can be deleted by the user and also during
the network gc run the network will automatically be cleaned up.
State of the persistent network that failed during creation is Allocated -
mysql> select * from networks where id='206' \G;
*************************** 1. row ***************************
id: 206
name: p2
uuid: 7779dedf-c6de-4958-9c78-04ec8f543383
display_text: p2
traffic_type: Guest
broadcast_domain_type: Vlan
broadcast_uri: NULL
gateway: 10.1.1.1
cidr: 10.1.1.0/24
mode: Dhcp
network_offering_id: 14
physical_network_id: 200
data_center_id: 1
guru_name: ExternalGuestNetworkGuru
state: Allocated
related: 206
domain_id: 1
account_id: 2
dns1: 10.103.128.15
dns2: NULL
guru_data: NULL
set_fields: 0
acl_type: Account
network_domain: cs2cloud.internal
reservation_id: 5621c241-31e7-487e-b09f-a851f526bf29
guest_type: Isolated
restart_required: 0
created: 2013-06-07 10:53:19
removed: NULL
specify_ip_ranges: 0
vpc_id: NULL
ip6_gateway: NULL
ip6_cidr: NULL
network_cidr: NULL
display_network: 1
network_acl_id: NULL
1 row in set (0.00 sec)
Persistent network offering of the network -
mysql> select * from network_offerings where id=14 \G;
*************************** 1. row ***************************
id: 14
name: Persistent
uuid: 48ab6777-6f26-4e8e-88eb-0bbaf0200949
unique_name: Persistent
display_text: Persistent
nw_rate: 200
mc_rate: 10
traffic_type: Guest
tags: NULL
system_only: 0
specify_vlan: 0
service_offering_id: NULL
conserve_mode: 1
created: 2013-06-07 10:22:58
removed: NULL
default: 0
availability: Optional
dedicated_lb_service: 1
shared_source_nat_service: 0
sort_key: 0
redundant_router_service: 0
state: Enabled
guest_type: Isolated
elastic_ip_service: 0
eip_associate_public_ip: 0
elastic_lb_service: 0
specify_ip_ranges: 0
inline: 0
is_persistent: 1
internal_lb: 0
public_lb: 1
1 row in set (0.00 sec)
> 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, 4.2.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
