** Update @ 4/14 16:30 PDT **
A change in the F5 API resulted in updated error code handling in our system. We've now pushed updates to the engine which deploys load balancers. A side-effect is that the lose artifacts of prior create/delete failed jobs must be cleaned up first. If you continue to experience problems, please open a case and refer to problem identified in case 00203213.
Load Balancer additions and deletions fail.
Presently we're investigating recent failed add and delete jobs for GoGrid Load Balancers. We'll update you when we have more information.
Until a resolution is reached, we suggest the following.
If a delete load balancer job failed:
The Load Balancer shouldn't be answering. If it is not answering, then use the same IP on your secondary public interface of a system that can answer (Local Area Connection 3 on Windows systems, and eth2 on Linux Systems). Please submit a case to GoGrid Support to clean up the remaining Load Balancer artifacts as your Load Balancer is only partially deleted. We can remove the bad database entries and clean up the hardware.
If you cannot deploy a load balancer:
Use the IP you would use on the Load Balancer as a secondary IP on your secondary public interface of your system (Local Area Connection 3 on Windows systems, and eth2 on Linux Systems).