Thanks for the replies. It turned out to be a consequence of "bmcsetup" being first in the "chain" variable (which was present because it had been created using the community edition of Platform Cluster Manager (which I was using at my boss' suggestion, but it has been a major time waster).
On Mon, Dec 16, 2019 at 4:17 PM Calvin Dodge <[email protected]> wrote: > > We've been deploying stateless RHEL 7.6 images to Dell nodes, > including older R620 and R630 units, and brand new R640s. > > On most of the nodes we're seeing very strange results. Instead of a > quick boot-up, we're seeing console messages (maybe dmesg output) that > seem to take much longer than expected (example - eth0 typically comes > online about 15 minutes after initial boot-up). > > The frustrating thing is that the deployments are identical, yet we > get different results depending on the node (so one R620 is fine, > while 3 more are stuck). > > Has anyone else seen this behavior. Can anyone else provide us a clue? > > Sincerely, > > Calvin Dodge _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
