LoadBalancer: troubleshooting
Load Balancer in provisioning_status = PENDING_CREATE or PENDING_UPDATE
When a load balancer is in provisioning_status PENDING_UPDATE or PENDING_CREATE, any
action on it is blocked from OpenStack. If the load balancer remains stuck in this
state it can’t be modified, recovered or deleted.
In this case, the loadbalancer has to be deleted by our sys admins. To solve the issue
please write to our support team (superc@cineca.it).
Load Balancer in provisioning_status = ERROR
When a load balancer is in provisioning_status ERROR something has failed in one or more of its
components (i.e. the amphora machines): if the error occurred on only one of the load balancer’s
amphora machines, the load balancer itself may be still operative but any modification operations
(including deletion) performed by the user will be prevented.
In order to solve this issue, the load balancer failover operation can be carried out by OpenStack
admins.
To solve the issue please write to our support team (superc@cineca.it).
Load Balancer in operating_status = DEGRADED
When a load balancer shows its operating_status equal to DEGRADED this means that an error has
occured to one or more of its pool member. This state does not necessarily compromise completely
the loadbalacer, it just means that the loadbalancer is not operating at maximum capacity.
The reason could be either:
at least one of the members is in
ERRORstateall the members are in
ACTIVEstate but there is some configuration or network error inside the virtual machine
Those problems should be solvable by the user since the problems depend on the inner workings of the member and
users have access to the member via ssh.
If the member is stuck in ERROR state, please write to our support team (superc@cineca.it).