pkommoju
commented
3 years ago - The IP range 10.0.x.y is blocked by default Security group picked during AWS VM setup. To resolve the problem, IP of the busybox containers is moved into 172.16.x.y.
- Add an explicit check for the services to actually be up and running by checking for the service ports to show up netstat. This is till not enough, so add another 2 minute delay. Later service status checking can look in the service log file for the message saying service has started.
- Skip adding neighbors to the goal state if there are no neighbors. S5 is fails without this change because while trying to build goal state, neighbor information is null in the subnet ports.