You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/04/18 14:23:15 UTC

[jira] [Commented] (CLOUDSTACK-6211) Xenserver - HA - SSVM fails to start due to running out of management Ip ranges when testing host down scenarios.

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

ASF subversion and git services commented on CLOUDSTACK-6211:
-------------------------------------------------------------

Commit bc9737ec8a949e1d01475ec5a7af26d8038994d5 in cloudstack's branch refs/heads/4.4 from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bc9737e ]

CLOUDSTACK-6211: Xenserver - HA - SSVM fails to start due to running out of management Ip ranges when testing host down scenarios

Signed-off-by: Koushik Das <ko...@apache.org>


> Xenserver - HA - SSVM fails to start due to running out of management Ip ranges when testing host down scenarios.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6211
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6211
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>            Reporter: Harikrishna Patnala
>            Assignee: Harikrishna Patnala
>             Fix For: 4.4.0
>
>
> Xenserver - HA - SSVM fails to start due to running out of management Ip ranges when testing host down scenarios.
> Set up:
> Advanced zone set up with 2 hosts in 1 cluster and 1 more host in another cluster.
> I have been performing test cases that involves host going down and up , so that HA of user Vms and System Vms happen.
> Currently SSVM is not able to start because of not having any free management Ip.
> DB shows that there are many ip addresses from the pod range that has been assigned to the SSVM( older SSVMs that are currently in "Destroyed" state).
> Database changed
> mysql> select * from nics where id in ( 7,22,23,3,4);
> ------------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------
> id 	uuid 	instance_id 	mac_address 	ip4_address 	netmask 	gateway 	ip_type 	broadcast_uri 	network_id 	mode 	state 	strategy 	reserver_name 	reservation_id 	device_id 	update_time 	isolation_uri 	ip6_address 	default_nic 	vm_type 	c reated 	removed 	ip6_gateway 	ip6_cidr 	secondary_ip 	display_nic
> ------------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------
> 3 	c3ac0565-e881-4900-8b52-f323935f1a1b 	18 	NULL 	NULL 	NULL 	NULL 	NULL 	NULL 	201 	Static 	Deallocating 	Start 	PodBasedNetworkGuru 	c8e4d764-f6ca-40b5 -8d25-c46170f5f7bd 	1 	2014-02-19 19:37:24 	NULL 	NULL 	0 	SecondaryStorageVm 	2 014-02-19 00:29:35 	2014-02-20 00:37:24 	NULL 	NULL 	0 	1
> 4 	7cb4375a-241d-4ed5-9024-761607f3862e 	18 	NULL 	NULL 	NULL 	NULL 	NULL 	NULL 	203 	Static 	Deallocating 	Start 	StorageNetworkGuru 	c8e4d764-f6ca-40b5 -8d25-c46170f5f7bd 	3 	2014-02-19 19:37:24 	NULL 	NULL 	0 	SecondaryStorageVm 	2 014-02-19 00:29:35 	2014-02-20 00:37:24 	NULL 	NULL 	0 	1
> 7 	93ed755c-8f47-4e52-8116-08af431535e8 	19 	06:84:0c:00:00:07 	10.223.59.76 	255.255.255.192 	10.223.5 9.65 	Ip4 	NULL 	201 	Static 	Reserved 	Start 	PodBasedNetworkGuru 	dc82d127-074a-470b -bee8-9bb9393e7cda 	1 	2014-02-24 18:02:55 	NULL 	NULL 	0 	ConsoleProxy 	2 014-02-19 00:31:35 	NULL 	NULL 	NULL 	0 	1
> 22 	67684964-1a8d-4b8f-b645-5e19eeaf86a9 	28 	NULL 	NULL 	NULL 	NULL 	NULL 	NULL 	201 	Static 	Deallocating 	Start 	PodBasedNetworkGuru 	dd6f0afb-97c5-44c1 -829f-3d209c95e53c 	1 	2014-02-24 18:03:20 	NULL 	NULL 	0 	SecondaryStorageVm 	2 014-02-20 00:37:25 	2014-02-24 23:03:20 	NULL 	NULL 	0 	1
> 23 	17ad1565-4aeb-4de7-8e94-c82aedc6d255 	28 	NULL 	NULL 	NULL 	NULL 	NULL 	NULL 	203 	Static 	Deallocating 	Start 	StorageNetworkGuru 	ff80bf7b-918b-4bba -9068-8d78c9ed3915 	3 	2014-02-24 18:03:20 	NULL 	NULL 	0 	SecondaryStorageVm 	2 014-02-20 00:37:25 	2014-02-24 23:03:20 	NULL 	NULL 	0 	1
> ------------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------
> 5 rows in set (0.00 sec)
> mysql> select * from op_dc_ip_address_alloc;
> ------------------------------------------------------------------------------------------------------------+
> id 	ip_address 	data_center_id 	pod_id 	nic_id 	reservation_id 	taken 	mac_address
> ------------------------------------------------------------------------------------------------------------+
> 1 	10.223.59.70 	1 	1 	7 	6f2e97eb-b980-4a37-a826-86dfc914ba96 	2014-02-21 02:14:42 	1
> 2 	10.223.59.71 	1 	1 	4 	23146cf1-32fc-4f29-9850-60314c035a43 	2014-02-20 00:21:06 	2
> 3 	10.223.59.72 	1 	1 	NULL 	NULL 	NULL 	3
> 4 	10.223.59.73 	1 	1 	22 	ff80bf7b-918b-4bba-9068-8d78c9ed3915 	2014-02-21 02:15:42 	4
> 5 	10.223.59.74 	1 	1 	22 	0506b7c3-994a-4593-af3b-ea42fdeba710 	2014-02-20 00:37:29 	5
> 6 	10.223.59.75 	1 	1 	23 	a7c8a4a8-7da9-45a0-bac4-0d3375694960 	2014-02-20 21:58:36 	6
> 7 	10.223.59.76 	1 	1 	7 	dc82d127-074a-470b-bee8-9bb9393e7cda 	2014-02-24 23:02:55 	7
> 8 	10.223.59.77 	1 	1 	3 	23146cf1-32fc-4f29-9850-60314c035a43 	2014-02-20 00:21:06 	8
> 9 	10.223.59.78 	1 	1 	22 	a7c8a4a8-7da9-45a0-bac4-0d3375694960 	2014-02-20 21:58:36 	9
> 10 	10.223.59.79 	1 	1 	7 	da7fdb59-750b-48a5-b459-7db5e8cfffeb 	2014-02-20 00:21:06 	10
> 11 	10.223.59.80 	1 	1 	23 	0506b7c3-994a-4593-af3b-ea42fdeba710 	2014-02-20 00:37:29 	11
> 12 	10.223.57.5 	1 	2 	NULL 	NULL 	NULL 	47
> 13 	10.223.57.6 	1 	2 	NULL 	NULL 	NULL 	48
> 14 	10.223.57.7 	1 	2 	NULL 	NULL 	NULL 	49
> 15 	10.223.57.8 	1 	2 	NULL 	NULL 	NULL 	50
> 16 	10.223.57.9 	1 	2 	NULL 	NULL 	NULL 	51
> 17 	10.223.57.10 	1 	2 	NULL 	NULL 	NULL 	52
> 18 	10.223.57.11 	1 	2 	NULL 	NULL 	NULL 	53
> 19 	10.223.57.12 	1 	2 	NULL 	NULL 	NULL 	54
> 20 	10.223.57.13 	1 	2 	NULL 	NULL 	NULL 	55
> 21 	10.223.57.14 	1 	2 	NULL 	NULL 	NULL 	56
> 22 	10.223.57.15 	1 	2 	NULL 	NULL 	NULL 	57
> 23 	10.223.57.16 	1 	2 	NULL 	NULL 	NULL 	58
> 24 	10.223.57.17 	1 	2 	NULL 	NULL 	NULL 	59
> 25 	10.223.57.18 	1 	2 	NULL 	NULL 	NULL 	60
> 26 	10.223.57.19 	1 	2 	NULL 	NULL 	NULL 	61
> 27 	10.223.57.20 	1 	2 	NULL 	NULL 	NULL 	62
> ------------------------------------------------------------------------------------------------------------+
> 27 rows in set (0.00 sec)
> mysql> select id,name,state from vm_instance;
> --------------------------
> id 	name 	state
> --------------------------
> 1 	v-1-VM 	Destroyed
> 2 	s-2-VM 	Destroyed
> 3 	s-3-VM 	Destroyed
> 4 	s-4-VM 	Destroyed
> 5 	s-5-VM 	Destroyed
> 6 	s-6-VM 	Destroyed
> 7 	s-7-VM 	Destroyed
> 8 	s-8-VM 	Destroyed
> 9 	s-9-VM 	Destroyed
> 10 	s-10-VM 	Destroyed
> 11 	s-11-VM 	Destroyed
> 12 	s-12-VM 	Destroyed
> 13 	s-13-VM 	Destroyed
> 14 	s-14-VM 	Destroyed
> 15 	s-15-VM 	Destroyed
> 16 	s-16-VM 	Destroyed
> 17 	s-17-VM 	Destroyed
> 18 	s-18-VM 	Destroyed
> 19 	v-19-VM 	Running
> 20 	test-1 	Running
> 21 	r-21-VM 	Running
> 22 	test-2 	Running
> 23 	TEST-3 	Running
> 24 	test-4 	Running
> 25 	new-1 	Running
> 26 	r-26-VM 	Running
> 27 	test-afterha 	Running
> 28 	s-28-VM 	Destroyed
> 29 	hello-1 	Stopped
> 30 	s-30-MyTestVM 	Destroyed
> 31 	s-31-MyTestVM 	Destroyed
> 32 	s-32-MyTestVM 	Destroyed
> 33 	s-33-MyTestVM 	Destroyed
> 34 	s-34-MyTestVM 	Destroyed
> 35 	s-35-MyTestVM 	Stopped
> --------------------------
> 35 rows in set (0.00 sec)



--
This message was sent by Atlassian JIRA
(v6.2#6252)