#4644 [fvt]2.10:makedhcp -a -d spents a long time to finish when node resolution has problem. Also Ctrl^c does not work when makedhcp -ad hang.

[junxiaw]

How to reproduce:
1.down the latest build
[root@c910f02c01p13 /]# lsdef -v
lsdef - Version 2.10 (git commit 4d7ca44ef5478fec45dbd325af6eec8a0789a2f3, built Wed Apr 15 01:19:37 EDT 2015)
[root@c910f02c01p13 /]# uname -a
Linux c910f02c01p13.pok.stglabs.ibm.com 3.10.0-123.el7.ppc64 #1 SMP Mon May 5 11:18:37 EDT 2014 ppc64 ppc64 ppc64 GNU/Linux
[root@c910f02c01p13 /]# cat /etc/*-release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.0 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.0"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.0 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.0:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.0
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION=7.0
Red Hat Enterprise Linux Server release 7.0 (Maipo)
Red Hat Enterprise Linux Server release 7.0 (Maipo)
[root@c910f02c01p13 /]#

2.makedhcp -a -d
-------------> will hang here
used ctr + c
910f02c01p14:/opt/xcat/share/xcat/tools/autotest/result # makedhcp -a -d
^Cc910f02c01p14:/opt/xcat/share/xcat/tools/autotest/result #
c910f02c01p14:/opt/xcat/share/xcat/tools/autotest/result # ps -aux |grep makedhcp
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
root 32218 0.0 1.0 51648 42048 ? S 07:22 0:00 xCATd SSL: makedhcp for root@localhost: dhcp in
root 32266 0.0 0.0 5312 2176 pts/0 S+ 07:30
-------------->could not stop it

[XiaoPeng Wang]

The root cause of the hang was the node IP resolution has problem, then omshell takes 10s for each node to finish the check. Setup the correct dns will solve this problem.

[XiaoPeng Wang]

When investigate this issue, Jun Xia found another issue that ctrl^c does not work for makedhcp -ad when it hang.

The root cause for this issue was the dhcp process was waiting for the omshell to exit, but omshell dif not receive the INT signal to exit. The fix was to make the dhcp process exit directly, then the omshell process will exit accordingly.

commit:
2.9.2 1b29f74
2.10 71a764e

[junxiaw]

tested