You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came from slack channel.
This came about investigating why our stateless Boston nodes (that get assigned static IPs), weren’t cycling their NICs after running confignetwork/configeth at boot. The NIC will be cycled if updatenode is called. According to the portion of configeth that appears to be responsible for this, it appears to only occur when $UPDATENODE is set or REBOOT=TRUE
if [ "$UPDATENODE" = "1" ] || grep "REBOOT=TRUE" /opt/xcat/xcatinfo >/dev/null 2>&1; then
if [ "$str_os_type" = "debian" ];then
ifdown --force $str_inst_nic
else
ifdown $str_inst_nic
fi
ifup $str_inst_nic
fi
if [ $? -ne 0 ]; then
log_error "ifup $str_inst_nic failed."
error_code=1
fi
exit $error_code
fi
So the question is, how can we ensure that the NICs are cycled so that they are actually statically set? As it is, they are still using dhclient and will undergo the dhcp refresh/renew/release cycle.
The text was updated successfully, but these errors were encountered:
bybai
changed the title
configeth does not down/up new ifcfg-* for installnic when diskless not reboot
configeth does not down/up new ifcfg-* for installnic when diskless reboot
Feb 22, 2019
bybai
changed the title
configeth does not down/up new ifcfg-* for installnic when diskless reboot
configeth does not reload new ifcfg-* for installnic when diskless reboot
Feb 22, 2019
This came from slack channel.
This came about investigating why our stateless Boston nodes (that get assigned static IPs), weren’t cycling their NICs after running confignetwork/configeth at boot. The NIC will be cycled if
updatenode
is called. According to the portion of configeth that appears to be responsible for this, it appears to only occur when$UPDATENODE
is set orREBOOT=TRUE
So the question is, how can we ensure that the NICs are cycled so that they are actually statically set? As it is, they are still using dhclient and will undergo the dhcp refresh/renew/release cycle.
The text was updated successfully, but these errors were encountered: