Network Not Coming Up in Instances

asked 2015-06-19 15:36:16 -0500

Richi gravatar image

updated 2015-07-05 18:20:08 -0500

I've done a pretty thorough search of the Q&A's here using as many keywords I can think of and can't seem to find an answer to my issue (though I'm finding a lot of people with similar issues but no resolution)

I've followed the Quickstart Guide in RDO for creating an allinone Openstack installation and configured it to work with an existing network. I have an existing network ( on my LAN to which this new CentOS 7 running OpenStack Kilo is connected. I followed the guide and made modifications to the startup scripts of my host OS to configure the br-ex bridge and enp7s0 interface as an interface on that bridge. I've also created a private network ( following the defaults of the guide). I've imported 3 different images (CentOS 7, Fedora 22 and CirrOS qcow2 images from the official repositories and started instances assigning private and public interfaces to all. In all cases, I cannot access the VM instances from my host (either via ICMP ping or SSH). I can access the console but cannot login as the images don't have passwords. The trick to override the passwords either via the Post-Creation script (password: mypassword) or the API ('nova root-password <instance-id>') don't seem to work (the last one resulting in a:

ERROR (HTTPNotImplemented): Unable to set password on instance (HTTP 501) (Request-ID: req-65fa3132-4003-45dd-ab15-4070404ed2f2)
). From the Fedora console-log, it looks like the network interfaces aren't coming up:
A start job is running for LSB: Bring up/down networking (1min 6s / 5min 3s)[K[[32m OK [0m] Started LSB: Bring up/down networking.
[[32m OK [0m] Reached target Network is Online.
 Starting Initial cloud-init job (metadata service crawler)...
[ 70.053248] cloud-init[614]: Cloud-init v. 0.7.6 running 'init' at Fri, 19 Jun 2015 20:02:43 +0000. Up 70.03 seconds.
[ 70.098909] cloud-init[614]: 2015-06-19 20:02:43,197 -[WARNING]: Route info failed: Unexpected error while running command.
[ 70.099204] cloud-init[614]: Command: ['netstat', '-rn']
[ 70.099384] cloud-init[614]: Exit code: 1
[ 70.099542] cloud-init[614]: Reason: -
[ 70.099700] cloud-init[614]: Stdout: 'Kernel IP routing table\nDestination Gateway Genmask Flags MSS Window irtt Iface\n'
[ 70.099859] cloud-init[614]: Stderr: ''
[ 70.122800] cloud-init[614]: ci-info: +++++++++++++++++++++++Net device info++++++++++++++++++++++++
[ 70.130341] cloud-init[614]: ci-info: +--------+-------+-----------+-----------+-------------------+
[ 70.136699] cloud-init[614]: ci-info: | Device | Up | Address | Mask | Hw-Address |
[ 70.136877] cloud-init[614]: ci-info: +--------+-------+-----------+-----------+-------------------+
[ 70.137122] cloud-init[614]: ci-info: | lo: | True | | | . |
[ 70.137325] cloud-init[614]: ci-info: | eth1: | False | . | . | fa:16:3e:8d:1e:65 |
[ 70.137525] cloud-init[614]: ci-info: | eth0: | True | . | . | fa:16:3e:50:a2:a6 |
[ 70.137717] cloud-init[614]: ci-info: +--------+-------+-----------+-----------+-------------------+
[ 70.137905] cloud-init[614]: ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[ 70.408174] cloud-init[614]: 2015-06-19 20:02:43,506 -[WARNING]: Calling '' failed [0/120s]: request error [('Connection aborted.', error(101, 'Network is unreachable'))]

(the last ... (more)

edit retag flag offensive close merge delete


You cannot access Nova Metadata-server. Hence cloud-init cannot obtain meta-data for instance and doesn't inject ssh keypair.

dbaxps gravatar imagedbaxps ( 2015-07-05 16:03:38 -0500 )edit

This message :-

[ 70.408174] cloud-init[614]: 2015-06-19 20:02:43,506 -[WARNING]: Calling '' failed [0/120s]: request error [('Connection aborted.', error(101, 'Network is unreachable'))]

is a fair.

dbaxps gravatar imagedbaxps ( 2015-07-05 16:04:16 -0500 )edit

2 answers

Sort by ยป oldest newest most voted

answered 2015-07-05 18:41:02 -0500

Richi gravatar image

Got it! The issue is that the guest VMs weren't getting the DHCPOFFER response from my internal network's DHCP server because of the way the OpenStack's Access & Security policies were configured. The step missing in the Quickstart Guide was to add an Ingress rule for Custom UDP using port 68!

Hope this helps other people having similar issues

edit flag offensive delete link more


By default for each private network it's own copy of DNSMASQ daemon is started by system and it doesn't require Access & Security policies to be configured. It sounds like you have your own DHCP server different from DNSMASQ.

dbaxps gravatar imagedbaxps ( 2015-07-06 00:47:36 -0500 )edit

answered 2015-06-22 02:18:02 -0500

Are you sure your cirros image does not have the "cubswin:)" password for the cirros account ? You then can use sudo afterwards to get root...

Be careful that your keyboard is mapped properly, I had problems typing this password with my french keyboard and needed:

openstack-config --set /etc/nova/nova.conf DEFAULT vnc_keymap fr
edit flag offensive delete link more


It took a while, but I was able to access the cirros image via the console! (It seems the console was blocking on the DHCP discovery of the IP addresses of the interfaces.

I was able to log in, but all I was able to confirm is that the instance wasn't getting its IP address from the DHCP server. I'

Richi gravatar imageRichi ( 2015-07-05 14:38:23 -0500 )edit

Hi, i'm also having issue of not getting any ip addresses from the dhcp server, was wondering if you have had any luck in resolving the issue?

Nazmi gravatar imageNazmi ( 2015-08-26 02:27:13 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2015-06-19 15:36:16 -0500

Seen: 3,312 times

Last updated: Jul 05 '15