Welcome to the Linux Foundation Forum!

Lab 4.1-Can not connect to golden instance

I have created golden instance, but can not access to that. Also, I am not sure what qrouter I should use? Can someone explain?

This is the netns list:

ubuntu@devstack-cc:~/devstack$ ip netns list

qrouter-f6724b39-ad39-4352-bc22-5aae4c911196

qdhcp-6348d867-6eda-45a4-8f9c-8a349b0c7f1f

qrouter-e46cedde-1835-4994-86b6-3c1b26371c78

qdhcp-cd2507b6-9659-488c-bc33-46cd6a34849e

 

Error message when I tried to use this command:

ubuntu@devstack-cc:~/devstack$ ip netns exec qrouter-f6724b39-ad39-4352-bc22-5aae4c9

11196 ssh cirros@10.10.128.12

seting the network namespace "qrouter-f6724b39-ad39-4352-bc22-5aae4c911196" failed:

Operation not permitted

This is from BUI:

.

Name
golden
ID
b759d24c-df6c-40cb-b4da-d6ca362ff502
Status
Active
Availability Zone
nova
Created
May 23, 2017, 2:11 p.m.
Time Since Created
3 minutes
Host
devstack-cc

Specs


Flavor Name
m1.tiny
Flavor ID
1
RAM
512MB
VCPUs
1 VCPU
Disk
1GB

IP Addresses


Private
10.10.128.12,  fdd3:a129:b300:0:f816:3eff:fe37:f47e

Security Groups


default
  • ALLOW IPv4 to 0.0.0.0/0
  • ALLOW IPv4 from default
  • ALLOW IPv6 from default
  • ALLOW IPv6 to ::/0

 

 

Comments

  • Ssiddiqu
    Ssiddiqu Posts: 7
    edited May 2017

    My problem is that when I run the ip netns list from devstack-cc host, I don't see the UUID of the router that is attached to the golden instance. Can some one explain?

  • corysmart
    corysmart Posts: 6
    edited August 2017

    Not sure if you figured this out but maybe this helps.  In the BUI go to Project > Network > Routers, and you should only see 1 listed called router1, click on it and that will bring up the overview for router1.  You are looking for the ID (it's the second line) and that should correlate to one of the qrouter's you see when you run ip netns list.

     

    Note, even when you are using the right namespace/UUID when you attempt to login to the golden instance it may still fail with a (connection timed out message).  I had to add a rule to allow SSH to the default security group to be able to successfully login.

Categories

Upcoming Training