Ask Your Question
0

instance cannot get ip address although it is displayed in dashboard [closed]

asked 2016-11-11 04:50:06 -0600

Ciarf gravatar image

Hi all! I set up an OS environment following the official documentation for Ubuntu 16.04 choosing to deploy Networking Option 1 (Provider networks). Now, this is my problem: whenever I create a new instance I can see its IP address in the dashboard (as you can see from https://s22.postimg.org/5j7wtc1up/Screenshot_from_2016_11_11_11_37_40.png (here)); however when I do ifconfig within such machine, using the dashboard console, I can see that no ip address has been assigned to such machine (as you can see from https://s22.postimg.org/6zjfbh4rl/Screenshot_from_2016_11_11_11_38_28.png (here)). Therefore i cannot ping that machine unless I manually assign it an IP (so far I've always assigned the same that i read from the dashboard). All neutron services seem active and running to me. https://s16.postimg.org/yne6hxmth/Screenshot_from_2016_11_11_11_46_19.png (This) is what i get when running neutron agent-list. Any idea about how to solve this issue? Thanks in advance dear community!

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Ciarf
close date 2016-11-16 03:26:55.132800

Comments

I don't see your screenshots, but it seems the instance is connected, just doesn't get the IP address. Something wrong with DHCP server? neutron-dhcp-agent.log perhaps?

Bernd Bausch gravatar imageBernd Bausch ( 2016-11-11 09:18:29 -0600 )edit

Hi Bernd and thank you for helping me. When running neutron agent-list i see that all agents are correctly up. However, in neutron-dhcp-agent.log i can see some warnings like this one:

Ciarf gravatar imageCiarf ( 2016-11-11 09:59:25 -0600 )edit

2016-11-11 12:25:42.438 15928 WARNING stevedore.named [req-09aab0f2-e0ce-43fc-a2cf-b016e95aa78a - - - - -] Could not load neutron.agent.linux.interface.BridgeInterfaceDriver

Ciarf gravatar imageCiarf ( 2016-11-11 10:00:10 -0600 )edit

The error is crucial and probably means that the configured DHCP driver is not found on your system. The driver is a class in ...../neutron/neutron/agent/linux/interface.py; check if such a file exists. If yes, I don't know why it's not found. If not, check again if you installed everything.

Bernd Bausch gravatar imageBernd Bausch ( 2016-11-12 00:54:23 -0600 )edit

I apologise for my ignorance but I have no idea where to find that path/file :(

Ciarf gravatar imageCiarf ( 2016-11-13 08:40:50 -0600 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2016-11-11 22:17:41 -0600

diltram gravatar image

May you provide the logs from cloud-init from your VM? Without that, there is no way how to find out what is going one there.

edit flag offensive delete link more

Comments

Hi Diltram, actually i'm using a standard Ubuntu ISO image so i suppose cloud-init is not installed..

Ciarf gravatar imageCiarf ( 2016-11-14 02:35:58 -0600 )edit

What document are you following to setup this ISO image? I believe you have already installed ISO image and converted to QCOW2 or VHD format and running it as Virtual Machine. I assume that VM is not getting the IP address properly. Right?

Beny gravatar imageBeny ( 2016-11-16 00:47:36 -0600 )edit
0

answered 2016-11-16 03:25:28 -0600

Ciarf gravatar image

I was getting crazy with this issue.. but finally i discovered that it was caused by a f*g broken cable towards the controller node!!! Changed it and everything is working fine :) Thank you all guys for trying to help me.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-11-11 04:50:06 -0600

Seen: 893 times

Last updated: Nov 16 '16