When connecting a VMware Advanced Loadbalancer or VMware AVI Load Balancer to VMware Cloud Director there are no errors. However, when the tenant is attempting to configure services for the ALB all services are greyed out despite standard or premium settings. There are no errors given in the UI.
Within the vcloud-container-debug.log the following error can be seen:
2025-02-18 14:31:45,512 | ERROR | pool-jetty-167554 | NsxAlbSystemLimitUtil | Cannot format message: Could not fetch system limits for given NSX-ALB version {}. Setting default values with version:{} | requestId=<request ID>,request=GET https://<VCD FQDN>/cloudapi/1.0.0/edgeGateways/urn:vcloud:gateway:<gateway UUID>/loadBalancer/...,requestTime=1739889104958,remoteAddress=<Request address>:41866,userAgent=vcd-openapi-client,accept=application/json;version 38.1
java.lang.IllegalArgumentException: can't parse argument number:
at java.base/java.text.MessageFormat.makeFormat(MessageFormat.java:1451)
at java.base/java.text.MessageFormat.applyPattern(MessageFormat.java:491)
at java.base/java.text.MessageFormat.<init>(MessageFormat.java:370)
at java.base/java.text.MessageFormat.format(MessageFormat.java:859)
at com.vmware.vcloud.logging.impl.Log4jLoggerImpl.log(Log4jLoggerImpl.java:273)
at com.vmware.vcloud.logging.impl.Log4jLoggerImpl.info(Log4jLoggerImpl.java:123)
at com.vmware.vcloud.logging.impl.Log4jLoggerImpl.info(Log4jLoggerImpl.java:113)
at com.vmware.vcloud.networking.utils.NsxAlbSystemLimitUtil.getNsxAlbSystemLimit(NsxAlbSystemLimitUtil.java:52)
...
Caused by: java.lang.NumberFormatException: For input string: ""
at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.base/java.lang.Integer.parseInt(Integer.java:662)
at java.base/java.lang.Integer.parseInt(Integer.java:770)
at java.base/java.text.MessageFormat.makeFormat(MessageFormat.java:1449)
... 194 more
VMware Cloud Director 10.6.x
NSX 4.2.x
ALB 30.2.1
There are two possible causes: either the ALB version is incompatible with VMware Cloud Director, or the ALB is not configured as a HTTP load balancer.
First ensure that the load balancer is configured as HTTP. If the issue persists please engage with Broadcom VCF support to ensure the interoperability is correct for the versions.