Instances doesn't get IP
Hi all,
I meet a problem with my Openstack infrastructure. It's an offline infrastructure, the controler node and compute doesn't have access to Internet. I follow this documentation for deployement (Queens Release): https://docs.openstack.org/install-guide/openstack-services.html (https://docs.openstack.org/install-gu...)
I follow all instruction for the installation of Keystone, glance, nova and neutron. After when I tried to deploy an instance, my instance doesn't get IP address. No error in log. In /var/lib/neutron/dhcp I see the IP address reserved for the instance.
I can join all folder you want for help me. First this is my configuration:
Controler: 2 interface:
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:1a:64:d0:34:be brd ff:ff:ff:ff:ff:ff
inet6 fe80::21a:64ff:fed0:34be/64 scope link
valid_lft forever preferred_lft forever
3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master brqa7f0e57c-d0 state UP group default qlen 1000
link/ether 00:1a:64:d0:34:c0 brd ff:ff:ff:ff:ff:ff
inet6 fe80::21a:64ff:fed0:34c0/64 scope link
valid_lft forever preferred_lft forever
4: enp4s0.748@enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:1a:64:d0:34:be brd ff:ff:ff:ff:ff:ff
inet 10.26.9.19/25 brd 10.26.9.127 scope global enp4s0.748
valid_lft forever preferred_lft forever
inet6 fe80::21a:64ff:fed0:34be/64 scope link
valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:26:3c:f1:3d brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 scope global docker0
valid_lft forever preferred_lft forever
8: tap39c1a9de-db@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master brq99275f2e-5a state UP group default qlen 1000
link/ether 56:a8:df:50:99:93 brd ff:ff:ff:ff:ff:ff link-netnsid 0
9: tapd75c2984-2e@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master brqa7f0e57c-d0 state UP group default qlen 1000
link/ether 7a:da:65:b4:1b:d0 brd ff:ff:ff:ff:ff:ff link-netnsid 1
10: tap475e0c42-1d@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master brq99275f2e-5a state UP group default qlen 1000
link/ether ca:71:3f:b1:e0:a0 brd ff:ff:ff:ff:ff:ff link-netnsid 2
11: brqa7f0e57c-d0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:1a:64:d0:34:c0 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.20/24 brd 192.168.10.255 scope global brqa7f0e57c-d0
valid_lft forever preferred_lft forever
inet6 fe80::189c:87ff:fec0:f839/64 scope link
valid_lft forever preferred_lft forever
12: tapa9663a5e-cd@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master brqa7f0e57c-d0 state UP group default qlen 1000
link/ether 76:96 ...
Can you share:
You could trace DHCP requests at different points between instance and dnsmasq process and find out where they (or DHCP replies) disappear.
I answer you in the next answer post .