For the first time, we used Server Automation to reboot a group of systems in sequential order. However, the job gets stuck on the first group because the status of the systems stays in PENDING RESTART or in “not reported” status, even though the server has rebooted and is back up. I’ve waited over an hour to and the status never changes. This prevents it from marking this group as complete in the automatin plan so that it can move to the next group for reboots. Is this a known issue? How can I fix this? We’re on v10.0.2.
Please see the screenshot (server uptime is 0 which means it rebooted). That was Group A and never moved on to Group B, C, D… We ended up stopping the task and taking another approach which was not ideal for restarting our systems.
This is our QA env where the BF root is a VM and also we have a single relay server that is also a VM located in the domestic region to handle about 600 systems including int’l regions. Is the case of simply adding more relays to address this issue?