Ask Your Question
0

Zun Cloudshell container wont start

asked 2019-02-15 06:37:58 -0500

BenvanDamme gravatar image

Hello,

i deployed openstack queens 6.1.1 with kolla-ansible. Now i added zun kuryr and etc. Everything seems to work fine on the first look. After the addition of zun horizon showed a new button "cloudshell". When i try to launch the cloudshell it trys to start "cloud-shell-admin-admin-Default-RegionOne" but fails with 

Docker internal error: 500 Server Error: Internal Server Error ("network 263044eb-6283-4c44-9fe9-60a3a682e766 is ambiguous (2 matches found based on name)").

This is the ID of my external network. Every other container, launched in an internal network, works fine.

Kind Regards

edit retag flag offensive close merge delete

Comments

Could you verify if you have any neutron network created in your tenant? If not, there is a script in Kolla to create such network:

. /etc/kolla/admin-openrc.sh
. /usr/local/share/kolla-ansible/init-runonce

Let me know if it doesn't help.

hongbin034 gravatar imagehongbin034 ( 2019-02-18 13:42:09 -0500 )edit

Do you have any other idea?

BenvanDamme gravatar imageBenvanDamme ( 2019-03-06 08:49:10 -0500 )edit
add a comment

2 answers

Sort by ยป oldest newest most voted
0

answered 2019-12-21 02:33:33 -0500

UHL-Services gravatar image

How did you solved this in the end?

edit flag offensive delete link more

Comments

There was no solution. I disabled the service.

BenvanDamme gravatar imageBenvanDamme ( 2020-01-16 10:18:10 -0500 )edit
add a comment
0

answered 2019-02-19 01:44:21 -0500

BenvanDamme gravatar image

Hello,

thank you for your answer. I have networks in my tenant.

+--------------------------------------+----------------------------------------------------+--------------------------------------+
| ID                                   | Name                                               | Subnets                              |
+--------------------------------------+----------------------------------------------------+--------------------------------------+
| 08124b99-4702-4f71-80e1-96eab81c1b65 | private                                            | c718e195-5bac-4ae7-ae55-aeb3a41f4586 |
| 263044eb-6283-4c44-9fe9-60a3a682e766 | ext-net                                            | 162024c1-8105-4d2a-9489-79c0fd51d816 |
| 2b9fedb2-1fb0-4ef0-a152-2edc8905258c | internal                                           | 49c21910-df3e-49f3-96ab-e3693b3f0fbf |
| 99b410f2-e1f3-4be3-be5e-539e5da81672 | containers                                         | 5a148356-9f22-40bc-830a-22204be74695 |
| a7eff057-ee56-4351-9ddc-182c68bb0db1 | kuryr-net-5a0bf60c                                 | f9fb6032-7298-451d-bfed-9017cb504a1f |
| cb4c7629-d1e6-4e6c-acaa-2f65b74a73cc | HA network tenant 9d3c125163aa48d8b78e3707364f8ed7 | a9fd3632-0ccf-45fd-853b-92003db1fafa |
+--------------------------------------+----------------------------------------------------+--------------------------------------+

The gbaad/openstack-client:alpine container started by the cloud_shell-button trys to start a port in the ext-net, but fails.

Docker internal error: 500 Server Error: Internal Server Error ("network 263044eb-6283-4c44-9fe9-60a3a682e766 is ambiguous (2 matches found based on name)").

Kind Regards

edit flag offensive delete link more

Comments

The error message said there are multiple networks in your tenant so zun doesn't know which network the cloudshell container should run on. The quickest work-around is to have the containershell container runs on tenant with one network.

hongbin034 gravatar imagehongbin034 ( 2019-04-27 11:49:46 -0500 )edit

And I created a ticket to track this issue: https://bugs.launchpad.net/zun-ui/+bu...

hongbin034 gravatar imagehongbin034 ( 2019-04-27 11:50:30 -0500 )edit

And where do i have to change the tenant of the container?

BenvanDamme gravatar imageBenvanDamme ( 2019-05-08 05:03:46 -0500 )edit
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2019-02-15 06:37:58 -0500

Seen: 210 times

Last updated: Feb 19 '19

Related questions

[ZUN] Access the container command giving 500 Internal Server Error

neutron floating IPs on RDO allinone

Cause for strange network config?

tap devices getting tagged to 4095

Multiple tenant_network_types

I can ping private IP. but I can't ping floating ip

Hosting Openstack on an AWS EC2 instance. Openstack VMs unable to access internet!

Instance Interface down

how to start with openstack code?

Can multiple l3-agent instances run on one host?