[Murano] Problem with environment deployment if user selects external network

[Anastasia Kuznetsova]

Steps to reproduce:
1. Log in web UI
2. Navigate to "Murano" > "Application Catalog" > "Environments"
3. Create new murano environment and select "net04_ext" as a default environment network
4. Add some application to it
5. Send it to deploy

Observed result:
Case 1: if user selects "Assign Floating IP" during application creation
Deployment of environment fails with following error:
2015-08-03 11:01:26 — [exceptions.EnvironmentError]: Unexpected stack state UPDATE_FAILED: NotFound: External network 93da4b38-053f-472b-99e6-b9a66cb448d9 is not reachable from subnet e23dc71e-2091-432b-a7e3-0cb04b2268b5. Therefore, cannot associate Port 01845024-64c8-4491-99c3-66af0bc2560b with a Floating IP.

"OS::Neutron::FloatingIP" resource creation failed

Case 2: if user doesn't select "Assign Floating IP"
Deployment has stuck: 2015-08-03 12:00:21 — [murano.common.exceptions.TimeoutException]: The Agent does not respondwithin 3600 seconds
Seems like IP was allocated to instance, but instance actually didn't get it
Here is a generated Heat template: http://paste.openstack.org/show/406741/

bug in upstream https://bugs.launchpad.net/murano/+bug/1483304

[Stan Lagun (slagun)]

This is caused by the fact that floating IPs cannot be allocated for subnets that do not have routers connecting them to the public networks. It seems that this validation algorithm thinks that public subnets are not connected to their networks. Don't know if that is right behavior but it is not Murano issue anyway.

The only thing that Murano could do is not to allow to choose public networks at all. However one may want to attach instance to public network without allocating floating IP. I don't know if it is a valid use case or no. So I don't know if we need to improve UI or just close this bug as invalid

[Serg Melikyan (smelikyan)]

I think we should verify that application works without assigning floating ip, and remove external network from list of available networks.

[Ekaterina Chernova (efedorova)]

+1, I can do it

[Stan Lagun (slagun)]

When instance attached to external network there is no connectivity to Murano RabbitMQ. So even if there is a small chance that there are still use cases to join external network I think the best decision for now would be to hide them from UI drop-down

[Ekaterina Chernova (efedorova)]

https://review.fuel-infra.org/#/c/10304/

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/10304
Submitter: mos-infra-ci <>
Branch: openstack-ci/fuel-7.0/2015.1.0

Commit: f1bea816e80717118afd64c2c8a723a647805512
Author: Ekaterina Chernova <email address hidden>
Date: Tue Aug 11 12:06:10 2015

Hide external networks while selecting network for the env

Change-Id: Ib43b3bc330035cdfd176788801325a687f7ebea6
Closes-Bug: #1480895

[Alexander Bochkarev (abochkarev)]

Verified with fuel-7.0-241-2015-08-27_03-02-45.iso

[magicboiz (magicboiz)]

Hi

I think I'm facing the same problem, but with MOS61, trying to deploy "kubernetes Cluster", deployment always fails, with:

2015-10-08 10:02:24 — Action deploy is scheduled
2015-10-08 10:02:30 — Creating Kubernetes Master
2015-10-08 10:02:30 — Creating Gateway node for Kubernetes services
2015-10-08 10:02:30 — Creating Kubernetes Node kube-2
2015-10-08 10:02:30 — Creating VMs for Kubernetes cluster
2015-10-08 10:02:30 — Setting up Kubernetes cluster
2015-10-08 10:06:22 — Configuring etcd master node
2015-10-08 11:06:23 — Deployment finished with errors
2015-10-08 11:06:23 — [murano.common.exceptions.TimeoutException]: The Agent does not respondwithin 3600 seconds

In my case, assigning or not floating IP address to kubernetes nodes/gateways seems to be the same.....

[Ekaterina Chernova (efedorova)]

Hi magicboiz, please create a separate bugs and attach murano logs. Thanks@