Multiple network found error in AWS LoadBalancer

[Malleshi C N]

Hi Heat Team,
I am working on Autoscaling using Heat templates. I am not able to create a stack , stack creation is failing with the below error.

" 2014-04-09 07:42:27.243 26960 TRACE heat.engine.resource Error: Resource create failed: BadRequest: Multiple possible networks found, use a Network ID to be more specific. (HTTP 400) (Request-ID: req-20ba46bc-02a9-4c5b-b762-fb39aa21b7e9)"

Error:
> 2014-04-09 07:42:27.195 26960 ERROR heat.engine.resource [-] CREATE : Instance "LB_instance"
>
> " 2014-04-09 07:42:27.243 26960 TRACE heat.engine.resource Error: Resource create failed: BadRequest: Multiple possible networks found, use a Network ID to be more specific. (HTTP 400) (Request-ID: req-20ba46bc-02a9-4c5b-b762-fb39aa21b7e9)"

Refer Question: https://answers.launchpad.net/ubuntu/+source/heat/+question/246865

[Thomas Herve (therve)]

Using VPCZoneIdentifier should work. Please show a template using them if not.

[Zane Bitter (zaneb)]

The problem is creating the LoadBalancer instance, not the Autoscaling group.

There doesn't appear to be a way to use the AWS::ElasticLoadBalancing::LoadBalancer resource with Neutron at present (unless there is only one Network), so IMO this is definitely a bug.

The workaround for now is to use the Neutron LBaaS resources instead.

[Sergey Kraynev (skraynev)]

I agree with Zane, that better solution is using Neutron LBaaS. However I have some questions about AWS LoadBalancer:

- Should we implement SubnetId property? Currently it has status not implemented, but I think that it should not be a big deal to turn on it. (My idea is pass it parameter to LB_instance in template by default it may be None).

- AVAILABILITY_ZONES property looks unused, but it is required. I have not found any place where it is used or passed to the child template. Could you clarify it?

[Sergey Kraynev (skraynev)]

I don't see any response from long time, so lrt's mark this bug as Won't Fix, with solution:
- use neutron LBaAS

[Arghya Banerjee (arbanerj)]

This needs to be fixed - we have a lot of users who deploy using cloud formation templates in AWS and OpenStack both - we cannot keep requesting users to use one for AWS and another template for OpenStack.

--Arghya