1 Reply Latest reply on Feb 27, 2019 3:59 AM by Devendra Dehadaraya

    Create Load Balancer in Service Blueprint throws cannot find Client network or Server Network

    Marcel Drechsler
      Share This:

      I'm trying to create a service blueprint (target environment AWS) which also contains a loadbalancer. I activated to "Define a new Load Balancer pool" and inserted all required information. The network container contains a load balancer, my network is also tagged. Unfortunately on provisioning, I receive an error:


      com.bmc.cloud.fsm.FSMException: Could not find any LogicalLoadBalancer which matches criteria of either Client network or Server Network.


      I can't explain myself this error. How is CLM doing a lookup for the Client Network / Server Network?


      Provisioning without a loadbalancer is working fine. Does anybody have a hint for me where to look at?