Ask Your Question

Revision history [back]

You wrote $ ssh cirros@192.168.1.201
cirros@192.168.1.201's password: 
$ nslookup www.google.com
Server:    172.21.21.2
Address 1: 172.21.21.2 host-172-21-21-2.openstacklocal

nslookup: can't resolve 'www.google.com'

Update your private network with DNS value of your real ISP. If it won't help
1. Drop VM
2. Recreate interface on router to your private network ( already updated)
It should come up in ACTIVE mode
3.Launch VM again, make sure `nslookup` works now.
You wrote $ ssh cirros@192.168.1.201
cirros@192.168.1.201's password: 
$ nslookup www.google.com
Server:    172.21.21.2
Address 1: 172.21.21.2 host-172-21-21-2.openstacklocal

nslookup: can't resolve 'www.google.com'

Update your private network with DNS value of your real ISP. If it won't help
1. Drop VM
2. Recreate interface on router to your private network ( already updated)
It should come up in ACTIVE mode
3.Launch VM again, make sure `nslookup` works now.

Next:-
qg-* should be the port of br-ex OVS bridge, qr-* should be the port of br-int OVS bridge on Neutron Server.
They are not present in `ovs-vsctl show`  report on Neutron Server Node.
You wrote $ ssh cirros@192.168.1.201
cirros@192.168.1.201's password: 
$ nslookup www.google.com
Server:    172.21.21.2
Address 1: 172.21.21.2 host-172-21-21-2.openstacklocal

nslookup: can't resolve 'www.google.com'

Update your private network with DNS value of your real ISP. If it won't help
1. Drop VM
2. Recreate interface on router to your private network ( already updated)
It should come up in ACTIVE mode
3.Launch VM again, make sure `nslookup` works now.

Next:-
qg-* should be the port of br-ex OVS bridge, qr-* should be the port of br-int OVS bridge on Neutron Server.
They are not present in `ovs-vsctl show`  report on Neutron Server Node.