We fixed this issues of nodes not booting completely, but now they don't set the deployment NIC's IP address.
The postscripts are defined only via groups, and I included "confignics" in the postscripts list. But when a node is deployed, and I login via the console, the deployment NIC has no IP address assigned to it. Perusing /var/log/xcat/xcat.log on the node in question shows the same order of postscripts as there were before I changed the postscripts assigned via the group in question, including at least one postscript which is not mentioned anywhere in the xCAT database or in any other script (disableconsistentNICrename). Could this be something the Platform Cluster Manager (community edition, version 4.3.0) is doing behind the scenes? What else could be hijacking the postscript list? Here's the current list of postscripts and postbootscripts. The image being deployed is RHEL 7.6 stateless: postbootscripts=setuppcm,syncfiles,ospkgs,otherpkgs,mountnfs,setupscratch,lsf_startup postscripts=syslog,remoteshell,syncfiles,confignics,setminiuidgid,mkresolvconf,setupntp,setnetboot Sincerely, Calvin Dodge _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
