Comment 2 for bug 1518137

Today Debugging this problem with Development (Sachin) and followup discussions below to be noted,
   1) Both Bug#1518137 and Bug#1519124, possibly narrow-down to same root-cause/theory and this is timing issue (inconsistent) depends on the sequence of DHCP request and VM powerON event and Plugin VM events processed and this could impact only for Guest-VM's which has less than 10 seconds max timeout for DHCP
   2) The possible contrail fix could help this if slightly lowering scan timer and Sachin prefer to put this only for 3.0 release to get more-tested and so for customer releases 2.21 and 2.22 we will release-note this bug for customer awareness

Release-Notes
#################
cirros-vm (or) any flavor of vm when having default of 9 seconds max timeout for DHCP from power-on, it may not get its IP address from Contrail DHCP during Power-on. The work-around is either to increase the DHCP max timeout configs (or) to request for new DHCP after power-on.