Private Cloud Load Balancer abnormal state

In Customer site , H3C Private Cloud Solution is deployed for their internal usage.

Customer reported that they created load balancer but it shows abnormal and also cannot see any entry of listener on F5 . 

During troubleshooting we found that it behavior is also abnormal. we tried to delet the new created load balancer which was in abnormal During troubleshooting, we observed abnormal behavior in the system. We attempted to delete the newly created load balancer that was in an abnormal state. Although the system displayed a success message after clicking the delete button, the load balancer still remained visible on the CloudOS page.

We observed that three IP addresses were available in the /27 subnet, but the load balancer creation still failed. From the logs, we identified that one additional IP address was required for SNAT.

We deleted one VM from the VPC to free up an IP address. After that, we created the load balancer again, and it worked normally.