Ask Your Question
0

Network unreachable on Fedora VM

asked 2016-04-11 14:20:10 -0600

Nenchy gravatar image

updated 2016-04-12 00:48:07 -0600

Bipin gravatar image

Hello,

I am new to OpenStack and I have problem that my Fedora VM instance doesn't get IP address. I have VirtualBox All-in-one Packstack installation on CentOS7. I don't see any Errors in logs, neither Nova, neither Neutron. I'm using ovs networking.

Correct error from Fedora instance is:

Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [116/120s]: request error [('Connection aborted.', OSError(101, 'Network is unreachable'))]

With nova list I see following:

+--------------------------------------+------------+--------+------------+-------------+--------------------+
| ID                                   | Name       | Status | Task State | Power State | Networks           |
+--------------------------------------+------------+--------+------------+-------------+--------------------+
| 0f9d37ac-6c16-4ee3-9623-654bcd1235ab | TestFedora | ACTIVE | -          | Running     | public=10.20.0.107 |
+--------------------------------------+------------+--------+------------+-------------+--------------------+

Which would lead me to believe that my instance has IP assigned, but while Fedora instance is booting I see error that network is no reachable.

Network listing

+--------------------------------------+---------+---------------------------------------------------+
| id                                   | name    | subnets                                           |
+--------------------------------------+---------+---------------------------------------------------+
| 6a98ab75-7b18-458a-b992-e627cc15b48b | public  | e66599db-a8fe-40e9-a185-62460955179d 10.20.0.0/24 |
| 32683122-bd69-4adc-b58e-ef1bbc33eb7e | private | 2809b588-b78e-49c9-b1e3-2b8c77007ad0 10.0.30.0/24 |
+--------------------------------------+---------+---------------------------------------------------+

I even went and on CentOS7 (where packstack all-in-one is installed) I disabled IPTABLES.

Please can somebody help me with further troubleshooting.

Thank you, Nenchy

edit retag flag offensive close merge delete

Comments

from the error, instance is not getting metadata as expected. Could you make sure, you have added proper security group rules for the instance ?

Bipin gravatar imageBipin ( 2016-04-12 00:49:02 -0600 )edit

Hello, so my instance is running in default security group:

public network | 10.20.0.107 security_groups | default

Which has TCP and UDP ports 1 - 65535 allowed from 0.0.0.0/0

Nenchy gravatar imageNenchy ( 2016-04-12 02:33:37 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-04-12 04:18:16 -0600

Nenchy gravatar image

updated 2016-04-13 05:27:39 -0600

I'm writing here since comment would be too short.

Now I'm able to get my IP to Fedora instance. I did the following

PUBLIC(10.20.0.0/24) <----> ROUTER (public interface: 10.20.0.100) <-------> PRIVATE (10.0.30.0/24)

Now when I booted machine I've got IP of 10.0.30.57. I assigned Floating IP from PUBLIC POOL 10.20.0.108

What now seems to be problem, is that I cannot reach from my workstation (where everything is installed) that IP - 10.20.0.108. Neither via PING and when I try to SSH it says: No Route to Host

I can PING 10.20.0.100 which is public interface on router.

Router config: [root@osaio log]# neutron router-show deee80db-215b-4480-b1b0-de4014fdfb67

| admin_state_up | True
| distributed | False
| external_gateway_info | {"network_id": "6a98ab75-7b18-458a-b992-e627cc15b48b", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "e66599db-a8fe-40e9-a185-62460955179d", "ip_address": "10.20.0.100"}]} | ha | False
| id | deee80db-215b-4480-b1b0-de4014fdfb67
| name | extrouter
| routes |
| status | ACTIVE
| tenant_id | 4d45f655b0ad4b7db998f80d957629f8

Do I need to add some routes somewhere? But shouldn't this already be done by Neutron automatically?

UPDATE:

The Thing is resolved by very "stupid" Action... And that is RESTART of neutron-l3-agent.

So the symptoms were following: - Everything seemd to be alright from perspective of configuration - From Router Namespace I was able to ping outside world, as well as, private IP of running VM instance - From Router Namespace I wasn't able to ping Floating IP address, but was able to ping public gateway - From Host where OpenStack was installed I wasn't able to ping Floating IP, but was able to ping public gateway

In short, everything seemd to be alright...

Thank you once more, Nenchy

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-04-11 14:20:10 -0600

Seen: 345 times

Last updated: Apr 13 '16