NetworkingInternalOperationError on new VM w/Load Balancer
Karel (Raskenlund)
0
Reputation points
We've had an environment running for ~2 years but since a few days ago suddenly we can no longer launch VMs that are attached to the Load Balancer. We have not made changes to the environment.
If we set up a new VM from an image and configure it to be in the Network Load Balancer Backend Pool, the VM will fail to start with a NetworkingInternalOperationError
We tried redeploy, reapply, restart, etc. without any success.
When we set up a new VM without connecting it to the Load Balancer, it can start, and is healthy. And if we later manually connect it to the LB, all is fine.
Sign in to answer