Ask Your Question

dbblackdiamond's profile - activity

2016-01-05 18:13:33 -0600 received badge  Famous Question (source)
2015-11-19 17:10:30 -0600 received badge  Enthusiast
2015-11-18 22:44:03 -0600 received badge  Notable Question (source)
2015-11-18 00:08:14 -0600 answered a question Neutron: Can't ping internet from instance and router namespace

Hi,

I have actually figured it out after much searching and head-scratching. The VMs Openstack is installed into are running in VirtualBox and by default, VirtualBox doesn't allow Promiscuous Mode on the VM network adapters. Once I set my external network adapter to allow Promiscuous Mode, it all started to work fine.

Thanks a lot for the responses. Bertrand.

2015-11-17 13:01:59 -0600 received badge  Supporter (source)
2015-11-17 13:01:11 -0600 received badge  Popular Question (source)
2015-11-17 10:47:17 -0600 commented answer Neutron: Can't ping internet from instance and router namespace

Hi, Thanks a lot for the response. I have just done that, restarted the services and even rebooted the virtual machines and it still doesn't work.

2015-11-16 19:37:34 -0600 asked a question Neutron: Can't ping internet from instance and router namespace

Hi,

I have been trying to configure an openstack kilo environment based on 4 virtual machines with the following network configuration:

  • Controller01: external ip 192.168.1.135, management ip 192.168.50.135, tunnel ip 192.168.60.135
  • Compute01: external ip 192.168.1.136, management ip 192.168.50.136, tunnel ip 192.168.60.136
  • Compute02: external ip 192.168.1.140, management ip 192.168.50.140, tunnel ip 192.168.60.140
  • Network01: no external ip as per installation guide, management ip 192.168.50.137, tunnel ip 192.168.60.137. The external interface is eth1

My issue is that I can't ping the internet or outside world from the instances or from the router namespace. My instance subnet is 10.10.10.0. My qrouter has 2 interfaces: 10.10.10.1 and 192.168.1.160.

From an instance, I can ping 10.10.10.1, 192.168.1.160 but not my default gateway, which is 192.168.1.1 or anything else on the 192.168.1.x network. From the instance, I can also ping another instance and from the namespace of the qrouter, I can ping the instance as well.

Here are some information from Network01:

root@network01:~# ip netns
qdhcp-5c2bd816-81b9-4c42-acf5-3103fdceabed
qrouter-88baa567-97f2-48be-883c-a7ae389a60c5

root@network01:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:40:7d:2a brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe40:7d2a/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovs-system state UP group default qlen 1000
    link/ether 08:00:27:6c:6f:1a brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a00:27ff:fe6c:6f1a/64 scope link 
       valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:4c:b3:63 brd ff:ff:ff:ff:ff:ff
    inet 192.168.50.137/24 brd 192.168.50.255 scope global eth2
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe4c:b363/64 scope link 
       valid_lft forever preferred_lft forever
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:7f:46:a3 brd ff:ff:ff:ff:ff:ff
    inet 192.168.60.137/24 brd 192.168.60.255 scope global eth3
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe7f:46a3/64 scope link 
       valid_lft ...
(more)
2015-10-14 07:40:24 -0600 received badge  Nice Question (source)
2015-07-24 03:24:04 -0600 received badge  Student (source)
2015-06-22 18:51:04 -0600 received badge  Famous Question (source)
2015-06-19 06:48:33 -0600 received badge  Notable Question (source)
2015-06-18 09:55:16 -0600 received badge  Popular Question (source)
2015-06-08 23:15:35 -0600 asked a question Error HTTP500 when running nova image-list

Hi,

I know this has been asked, but I couldn't post all the info I wanted as a reply, so I decided to post a new question. I am running a new install of Kilo on Ubuntu 14.04 LTS. I have been following the step-by-step installation guide provided on http://openstack.org and I have hit a snag. I am running everything on a single machine with a single network card and the IP address of that machine is 192.168.1.100. I have installed, configured and verified the proper operations of Keystone and Glance, meaning I can do the following:

root@openstack01:~# openstack user list
+----------------------------------+--------+
| ID                               | Name   |
+----------------------------------+--------+
| 54322530e93341b4bdc033fc82c7eec0 | demo   |
| 92cfda6c84e542268b67d926d4763c10 | admin  | 
| c879112bf5844e6db28a69f56f5a1251 | glance |
| f3b4043962e746ceb701679ce657f7e1 | nova   |
+----------------------------------+--------+
root@openstack01:~# openstack endpoint list
+----------------------------------+-----------+--------------+--------------+
| ID                               | Region    | Service Name | Service Type |
+----------------------------------+-----------+--------------+--------------+
| 56d21b506a2c4c0ab62cb7e44fbb4ed0 | RegionOne | keystone     | identity     |
| 964bd068b32b4dfba498eb8f915c5c58 | RegionOne | glance       | image        |
| de455c7f45644971bf7e75349b1bd7ed | RegionOne | nova         | compute      |
+----------------------------------+-----------+--------------+--------------+
root@openstack01:~# glance image-list
+--------------------------------------+---------------------+
| ID                                   | Name                |
+--------------------------------------+---------------------+
| d7dee9c8-404f-4548-836c-2cbe7f63919b | CentOS 7 x86_64     |
| 0447b0a9-36c1-47d9-aedd-04eab2983b22 | cirros-0.3.4-x86_64 |
+--------------------------------------+---------------------+
root@openstack01:~# nova endpoints
WARNING: glance has no endpoint in ! Available endpoints for this service:
+-----------+----------------------------------+
| glance    | Value                            |
+-----------+----------------------------------+
| id        | 4b040ee32a9c42f697646136cec24e4d |
| interface | public                           |
| region    | RegionOne                        |
| region_id | RegionOne                        |
| url       | http://192.168.1.100:9292        |
+-----------+----------------------------------+
+-----------+----------------------------------+
| glance    | Value                            |
+-----------+----------------------------------+
| id        | 7158c584bcc6488799e2df043c57441a |
| interface | internal                         |
| region    | RegionOne                        |
| region_id | RegionOne                        |
| url       | http://192.168.1.100:9292        |
+-----------+----------------------------------+
+-----------+----------------------------------+
| glance    | Value                            |
+-----------+----------------------------------+
| id        | 7b76501a10f44823801038da812abf7e |
| interface | admin                            |
| region    | RegionOne                        |
| region_id | RegionOne                        |
| url       | http://192.168.1.100:9292        |
+-----------+----------------------------------+
WARNING: nova has no endpoint in ! Available endpoints for this service:
+-----------+---------------------------------------------------------------+
| nova      | Value                                                         |
+-----------+---------------------------------------------------------------+
| id        | 2c14e44e747e49eeb79c94541eadff91                              |
| interface | public                                                        |
| region    | RegionOne                                                     |
| region_id | RegionOne                                                     |
| url       | http://192.168.1.100:8774/v2/e8a68a367640454e9d4608d77a2cf16b |
+-----------+---------------------------------------------------------------+
+-----------+---------------------------------------------------------------+
| nova      | Value                                                         |
+-----------+---------------------------------------------------------------+
| id        | 93143152026c46939fc9d6363cc6d38a                              |
| interface | admin                                                         |
| region    | RegionOne                                                     |
| region_id | RegionOne                                                     |
| url       | http://192.168.1.100:8774/v2/e8a68a367640454e9d4608d77a2cf16b |
+-----------+---------------------------------------------------------------+
+-----------+---------------------------------------------------------------+
| nova      | Value                                                         |
+-----------+---------------------------------------------------------------+
| id        | a65bdb9eb9c14df0b0c87393d9e102b4                              |
| interface | internal                                                      |
| region    | RegionOne                                                     |
| region_id | RegionOne                                                     |
| url       | http://192.168.1.100:8774/v2/e8a68a367640454e9d4608d77a2cf16b |
+-----------+---------------------------------------------------------------+
WARNING: keystone has no endpoint in ! Available endpoints for this service:
+-----------+----------------------------------+
| keystone  | Value                            |
+-----------+----------------------------------+
| id        | 325dea93a97c4575949d7b9e7312238f |
| interface | internal                         |
| region    | RegionOne                        |
| region_id | RegionOne                        |
| url       | http://192.168.1.100:5000/v2.0   |
+-----------+----------------------------------+
+-----------+----------------------------------+
| keystone  | Value                            |
+-----------+----------------------------------+
| id        | af4fc25b4bf049c7bc943444815182c0 |
| interface | public                           |
| region    | RegionOne                        |
| region_id | RegionOne                        |
| url       | http://192.168.1.100:5000/v2.0   |
+-----------+----------------------------------+
+-----------+----------------------------------+
| keystone  | Value                            |
+-----------+----------------------------------+
| id        | f61fb8a6c5914f8b9ce5dc783bfb8252 |
| interface | admin                            |
| region    | RegionOne                        |
| region_id | RegionOne                        |
| url       | http://192.168.1.100:35357/v2.0  |
+-----------+----------------------------------+
root@openstack01:~# nova service-list
+----+------------------+-------------+----------+---------+-------+----------------------------+-----------------+
| Id | Binary           | Host        | Zone     | Status  | State | Updated_at                 | Disabled Reason |
+----+------------------+-------------+----------+---------+-------+----------------------------+-----------------+
| 1  | nova-cert        | openstack01 | internal | enabled | up    | 2015-06-03T17:11:39.000000 | -               |
| 2  | nova-consoleauth | openstack01 | internal | enabled | up    | 2015-06-03T17:11:39.000000 | -               |
| 3  | nova-scheduler   | openstack01 | internal | enabled | up    | 2015-06-03T17:11:40.000000 | -               |
| 4  | nova-conductor   | openstack01 | internal | enabled | up    | 2015-06-03T17:11:40.000000 | -               |
| 6  | nova-compute     | openstack01 | nova     | enabled | up    | 2015-06-03T17:11:41.000000 | -               |
+----+------------------+-------------+----------+---------+-------+----------------------------+-----------------+

But then, when I do this, it fails:

root@openstack01:~# nova --debug image-list
DEBUG (session:195) REQ: curl -g -i -X GET http://192.168.1.100:35357/v3 -H "Accept: application/json" -H "User-Agent: python-keystoneclient"
INFO (connectionpool:188) Starting new HTTP connection (1): 192.168.1.100
DEBUG (connectionpool:362) "GET /v3 HTTP/1.1" 200 253
DEBUG (session:223) RESP: [200] content-length: 253 vary: X-Auth-Token keep-alive: timeout=5, max=100 server: Apache/2.4.7 (Ubuntu) connection ...
(more)
2015-06-08 23:15:35 -0600 answered a question nova image-list returns HTTP 500

This is just a shot in the dark, but a request is not made properly. Here is what I am seeing from your log: - first, nova makes a proper connection to get the image details: http://cont1:8774/v2/15888f03c6c94a3092accd3f3d0d1775/images/detail (http://cont1:8774/v2/15888f03c6c94a30...) - but then for some reason, it switches to the wrong port here: http://cont1:80/v1/images/detail?is_public=none&limit=20 (http://cont1:80/v1/images/detail?is_p...) .

This to me, seems like you have a configuration issue somewhere in the stack to explain the switch between the 2 or I might totally be out to lunch on this.

2015-06-08 23:15:35 -0600 commented question nova image-list returns HTTP 500

Hi,

I am having a similar issue, but I am not getting the "Connection Refused" error. Should I post a new question?