Lot of Guest-VM's across different Computes when Power-On, not receiving its Virtual-Network IP from Contrail DHCP
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Won't Fix
|
Critical
|
Unassigned | |||
R2.21.x |
Won't Fix
|
Critical
|
Unassigned | |||
Trunk |
New
|
Medium
|
Andra Cismaru |
Bug Description
For some of requirements like VM cloning etc, we need to have power-off Guest-VM's being recommended procedure. When power-up
~900 VM's which is part of 7 different Computes, I see Guest VM not receiving its Virtual-Network IP from Contrail DHCP
This Bug most likely not related to Bug# 1518137 because of below reasons and so opening this for tracking,
>> In Bug# 1518137, it is on Single Esx host/Compute and when this same tests tried on different Esx host/compute, the issue not seen prooving issue only related to "Maintainence Mode" recovery of Esx
>> This new Bug not setting any Esx on Maintaience and instead try only hundreds of Guest VM Power-off and Power-on part of routines which need this like Cloning etc. Mostly this new bug could be Performance issue handling hundreds of Guest VM's DHCP
Topology
##########
3 controllers
8 Esx nodes
### Debugging
root@oblocknode
2015-11-23 13:00:28,466 - INFO [pool-1-
2015-11-23 13:00:28,485 - INFO [pool-1-
2015-11-23 13:00:28,485 - INFO [pool-1-
root@oblocknode
root@oblocknode
root@oblocknode
### Version
root@oblocknode
root@oblocknode
root@oblocknode
Package Version Build-ID | Repo | Package Name
-------
contrail-analytics 2.21-103 103
contrail-config 2.21-103 103
contrail-control 2.21-103 103
contrail-dns 2.21-103 103
contrail-f5 2.21-103 103
contrail-
contrail-
contrail-
contrail-lib 2.21-103 103
contrail-nodemgr 2.21-103 103
contrail-
contrail-
contrail-
contrail-
contrail-setup 2.21-103 103
contrail-utils 2.21-103 103
contrail-
contrail-
contrail-
contrail-web-core 2.21-103 103
ifmap-python-client 0.1-2 103
ifmap-server 0.3.2-1contrail1 103
python-contrail 2.21-103 103
root@oblocknode
root@oblocknode
no longer affects: | juniperopenstack/r3.0 |
Changed in juniperopenstack: | |
milestone: | r3.0-fcs → none |
Changed in juniperopenstack: | |
status: | New → Won't Fix |
-bash-4.1$
-bash-4.1$ hostname
centos-build02
-bash-4.1$
-bash-4.1$ pwd
/users/nsarath/PR/Bug-1519124
-bash-4.1$
-bash-4.1$ ls -l
total 2661268
-rwxrwxrwx 1 nsarath test 1072435200 Nov 23 13:32 Ctrl-A-log.tar*
-rwxrwxrwx 1 nsarath test 982466560 Nov 23 13:32 Ctrl-B-log.tar*
-rwxrwxrwx 1 nsarath test 433827840 Nov 23 13:31 Ctrl-C-log.tar*
-rwxrwxrwx 1 nsarath test 28579840 Nov 23 13:41 Vrtr-0-log.tar*
-rwxrwxrwx 1 nsarath test 27893760 Nov 23 13:31 Vrtr-1-log.tar*
-rwxrwxrwx 1 nsarath test 28026880 Nov 23 13:31 Vrtr-2-log.tar*
-rwxrwxrwx 1 nsarath test 25937920 Nov 23 13:31 Vrtr-3-log.tar*
-rwxrwxrwx 1 nsarath test 28692480 Nov 23 13:31 Vrtr-4-log.tar*
-rwxrwxrwx 1 nsarath test 28856320 Nov 23 13:31 Vrtr-5-log.tar*
-rwxrwxrwx 1 nsarath test 29194240 Nov 23 13:31 Vrtr-7-log.tar*
-rwxrwxrwx 1 nsarath test 28477440 Nov 23 13:31 Vrtr-8-log.tar*
-bash-4.1$