[Fullstack] Respawn dhclient process in case of error
When dhclient process is started as async process by fake machine resource,
it might happen that "None" will be returned as first line of output
from this process. This is treated as an error and dhclient is halted
immediately.
Because of that fake machine don't have configured IP address and
test fails.
This patch adds "respawn_timeout" value set to 5 seconds for dhclient
async process. When dhclient process is restarted it should works fine
and IP address should be then configured properly.
Reviewed: https:/ /review. openstack. org/545820 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=92959238a3e 408e810ccd4f3d3 d453a35afb5bba
Committed: https:/
Submitter: Zuul
Branch: master
commit 92959238a3e408e 810ccd4f3d3d453 a35afb5bba
Author: Sławek Kapłoński <email address hidden>
Date: Mon Feb 19 13:28:57 2018 +0100
[Fullstack] Respawn dhclient process in case of error
When dhclient process is started as async process by fake machine resource,
it might happen that "None" will be returned as first line of output
from this process. This is treated as an error and dhclient is halted
immediately.
Because of that fake machine don't have configured IP address and
test fails.
This patch adds "respawn_timeout" value set to 5 seconds for dhclient
async process. When dhclient process is restarted it should works fine
and IP address should be then configured properly.
Change-Id: Ie056578abbe6e1 8c8415c6e61d755 f2248a70541
Closes-Bug: #1728948