{"push_id":619741782,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"5aa5b1ad8bdc5401dbe67cc52c08e5a2f01362bb","before":"701aac003558442c8e81550a36281e8421eaac03","commits":[{"sha":"d3b4eedcd3d5023704eef52a9307160c32b78dfc","author":{"email":"ed277fd86bc77a4a1e382c4bd5d43fdac47cc971@mirantis.com","name":"Dennis Dmitriev"},"message":"Add check for DHCP lease that remains after deletion the instance\n\n1) With nova-network, when an instance is migrated from one compute\nnode to another, it's DHCP lease remains on the first compute even\nafter instance is deleted.\nThis makes it impossible to obtain the same address for a new\ninstance with another MAC address which is created on the first\ncompute node.\n\nThe check will fail the test if the DHCP lease still remains on the\nfirst compute node after instance migration.\n\n2) Added @retry decorator to the method execute_through_host()\n\n3) Fixed issue with ping 8.8.8.8 (address wasn't provided to the\ncommand)\n\nChange-Id: I274f1ce9fda05f16eadd1cdbe4899b10639573ca\nRelated-Bug: #1391010","distinct":true,"url":"https://api.github.com/repos/stackforge/fuel-qa/commits/d3b4eedcd3d5023704eef52a9307160c32b78dfc"},{"sha":"5aa5b1ad8bdc5401dbe67cc52c08e5a2f01362bb","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Add check for DHCP lease that remains after deletion the instance\"","distinct":true,"url":"https://api.github.com/repos/stackforge/fuel-qa/commits/5aa5b1ad8bdc5401dbe67cc52c08e5a2f01362bb"}]}