On a compute node, xcat's confignetwork -s postscript creates ifcfg files named ifcfg-xcat-
But the corresponding route file is named route- which causes the routes to not be populated
Changing the routeop script in xcatpost scripts line
294 filename="/etc/sysconfig/network-scripts/route-$ifname"
to
295 filename="/etc/sysconfig/network-scripts/route-xcat-$ifname"
corrects this as a brute force method when confignetwork -s is used, but logic is needed to check if confignetwork is used with -s switch or not. Without the -s switch, the interface name has been left asifcfg-<ifname>, but with the -s switch, the name is changed to if ifcfg-xcat-<ifname>.
kjhee43
commented
2 years ago
When a node has a postscript combination of:
=confignetwork -s,setroute replace,syslog,remoteshell,syncfilesthe issue in the title presents.
On a compute node, xcat's confignetwork -s postscript creates ifcfg files named ifcfg-xcat-
But the corresponding route file is named route- which causes the routes to not be populated
Changing the routeop script in xcatpost scripts line
294 filename="/etc/sysconfig/network-scripts/route-$ifname"to
295 filename="/etc/sysconfig/network-scripts/route-xcat-$ifname"corrects this as a brute force method when confignetwork -s is used, but logic is needed to check if confignetwork is used with -s switch or not. Without the -s switch, the interface name has been left as
ifcfg-<ifname>, but with the -s switch, the name is changed to ififcfg-xcat-<ifname>.