Ask Your Question

grmarxer's profile - activity

2015-07-30 13:25:26 -0500 received badge  Famous Question (source)
2015-07-23 10:26:42 -0500 commented answer Juno Neutron MAC and IP assigned but IP missing on instance

Which logs would you like to see?

2015-07-23 08:13:11 -0500 received badge  Famous Question (source)
2015-07-22 01:56:51 -0500 received badge  Student (source)
2015-07-22 01:56:46 -0500 received badge  Self-Learner (source)
2015-07-22 01:56:46 -0500 received badge  Teacher (source)
2015-07-21 14:04:25 -0500 answered a question Juno Neutron MAC and IP assigned but IP missing on instance

My issue was I was trying to use GRE on a one node system. With a one node system there is only one OVS bridge, thus the DHCP request was going from the VM-TAP -> br-int -> tap port for DNSMASQ. Whereas with GRE it should go from br-int to br-tun. I redid my ml2.conf. ini file for vlans and deleted br-tun from OVS. Settings below. All other instructions identical to http://docs.openstack.org/juno/install-guide/install/apt/content/section_neutron-networking.html (http://docs.openstack.org/juno/instal...)

OVS Commands 
ovs-vsctl add-br br-eth1

ml2.conf.ini

[ml2]
type_drivers = flat,vlan
tenant_network_types = vlan
mechanism_drivers = openvswitch

[ml2_type_flat]
flat_networks = external

[ml2_type_vlan]
network_vlan_ranges = physnet2:100:110

[ovs]
tenant_network_type = vlan
network_vlan_ranges = physnet2:100:110
integration_bridge = br-int
bridge_mappings = external:br-ex
bridge_mappings = physnet2:br-eth1
2015-07-21 13:58:36 -0500 received badge  Notable Question (source)
2015-07-17 11:54:31 -0500 commented answer Juno Neutron MAC and IP assigned but IP missing on instance

Yes. Lots of post with no answers. Not very helpful

2015-07-17 11:53:30 -0500 received badge  Popular Question (source)
2015-07-16 18:17:29 -0500 asked a question Juno Neutron MAC and IP assigned but IP missing on instance

Hi Experts.

I have created an cirros instance and neutron has assigned a MAC and IP to that instance.

root@OneNode:/var/log/neutron# neutron port-show 8dbe9ccf-5d91-4c39-a147-a9d1b0567c0c
+-----------------------+------------------------------------------------------------------------------------+
| Field                 | Value                                                                              |
+-----------------------+------------------------------------------------------------------------------------+
| admin_state_up        | True                                                                               |
| allowed_address_pairs |                                                                                    |
| binding:host_id       | OneNode                                                                            |
| binding:profile       | {}                                                                                 |
| binding:vif_details   | {"port_filter": true, "ovs_hybrid_plug": true}                                     |
| binding:vif_type      | ovs                                                                                |
| binding:vnic_type     | normal                                                                             |
| device_id             | e9c92e0e-bf00-4f3e-871a-56d1efa2aac5                                               |
| device_owner          | compute:None                                                                       |
| extra_dhcp_opts       |                                                                                    |
| fixed_ips             | {"subnet_id": "8e214187-30e1-47b9-b615-5df74bfe6fa7", "ip_address": "10.10.200.5"} |
| id                    | 8dbe9ccf-5d91-4c39-a147-a9d1b0567c0c                                               |
| mac_address           | fa:16:3e:09:0b:00                                                                  |
| name                  |                                                                                    |
| network_id            | 8750341e-1174-408e-ab68-cc366f6d2166                                               |
| security_groups       | 94c15e68-d9af-4c1f-89ee-ac2be1a56330                                               |
| status                | ACTIVE                                                                             |
| tenant_id             | dbac7bfed36c4b7283c7187d43833f3b                                                   |
+-----------------------+------------------------------------------------------------------------------------+

If I look at ifconfig on the instance itself I see the MAC is correct but the IP address is not assigned. All of my logs are clean. Any ideas on where to look to determine why the IP address is not present on the instance but the MAC address is correct?

2015-07-06 10:44:18 -0500 received badge  Enthusiast
2015-07-05 22:59:29 -0500 received badge  Notable Question (source)
2015-07-02 07:50:39 -0500 received badge  Popular Question (source)
2015-06-30 23:44:29 -0500 asked a question Juno Controller RabbitMQ v3.4.2 but Compute Node v3.33 RPC error?

Hi Experts,

I have a three node Juno system running on Ubuntu 14.04. On the compute node I keep getting the following Endpoint does not support RPC version 3.33 to caller error when I launch a Nova instance. The Controller is running rabbitMQ v3.4.2. So I do not understand why the compute node thinks the endpoint does not support v3.33. I tried both rabbitMQ v3.3.3 and v3.5 on the compute node with the same result. Data below. Any suggestions?


    Nova Compute log
2015-06-30 21:10:32.072 3805 ERROR oslo.messaging.rpc.dispatcher [-] Exception during message handling: Endpoint does not support RPC version 3.33
2015-06-30 21:10:32.072 3805 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last):
2015-06-30 21:10:32.072 3805 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply
2015-06-30 21:10:32.072 3805 TRACE oslo.messaging.rpc.dispatcher     incoming.message))
2015-06-30 21:10:32.072 3805 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 185, in _dispatch
2015-06-30 21:10:32.072 3805 TRACE oslo.messaging.rpc.dispatcher     raise UnsupportedVersion(version)
2015-06-30 21:10:32.072 3805 TRACE oslo.messaging.rpc.dispatcher UnsupportedVersion: Endpoint does not support RPC version 3.33
2015-06-30 21:10:32.072 3805 TRACE oslo.messaging.rpc.dispatcher
2015-06-30 21:10:32.074 3805 ERROR oslo.messaging._drivers.common [-] Returning exception Endpoint does not support RPC version 3.33 to caller
2015-06-30 21:10:32.074 3805 ERROR oslo.messaging._drivers.common [-] ['Traceback (most recent call last):\n', '  File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply\n    incoming.message))\n', '  File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 185, in _dispatch\n    raise UnsupportedVersion(version)\n', 'UnsupportedVersion: Endpoint does not support RPC version 3.33\n']

root@controller:/etc/rabbitmq# rabbitmqctl status
Status of node rabbit@controller ...
[{pid,4015},
 {running_applications,[{rabbit,"RabbitMQ","3.4.2"},
                        {os_mon,"CPO  CXC 138 46","2.2.14"},
                        {mnesia,"MNESIA  CXC 138 12","4.11"},
                        {xmerl,"XML parser","1.3.5"},
                        {sasl,"SASL  CXC 138 11","2.3.4"},
                        {stdlib,"ERTS  CXC 138 10","1.19.4"},
                        {kernel,"ERTS  CXC 138 10","2.16.4"}]},
 {os,{unix,linux}},

 root@controller:~# nova service-list
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| Id | Binary           | Host       | Zone     | Status  | State | Updated_at                 | Disabled Reason |
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| 1  | nova-cert        | controller | internal | enabled | up    | 2015-07-01T04:12:35.000000 | -               |
| 2  | nova-scheduler   | controller | internal | enabled | up    | 2015-07-01T04:12:35.000000 | -               |
| 3  | nova-consoleauth | controller | internal | enabled | up    | 2015-07-01T04:12:35.000000 | -               |
| 4  | nova-conductor   | controller | internal | enabled | up    | 2015-07-01T04:12:36.000000 | -               |
| 5  | nova-compute     | Compute1   | nova     | enabled | up    | 2015-07-01T04:12:38.000000 | -               |
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
root@controller:~# neutron agent-list
+--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
| id                                   | agent_type         | host     | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
| 757fe28f-4e2d-4c64-909a-12a469d08df5 | Open vSwitch agent | network  | :-)   | True           | neutron-openvswitch-agent |
| 9eb4fb07-d76b-4924-adad-7cf2124a42ba | DHCP agent         | network  | :-)   | True           | neutron-dhcp-agent        |
| a1230bdb-e996-408c-bd93-d38f66080348 | L3 agent           | network  | :-)   | True           | neutron-l3-agent          |
| cce377eb-2df3-4252-b44f-9c46ed6fc192 | Metadata agent     | network  | :-)   | True           | neutron-metadata-agent    |
| e3b43ef5-2c81-4bd5-8938-0b9411c85a96 | Open vSwitch agent | Compute1 | :-)   | True           | neutron-openvswitch-agent |
+--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
2015-06-30 17:01:57 -0500 received badge  Notable Question
2015-06-30 10:14:26 -0500 received badge  Popular Question
2015-06-29 15:08:51 -0500 commented answer juno nova instance stuck in BUILD scheduling

I am having the same issue. I updated rabbitMQ but that did not help. I see nothing glaring in the log debug messages. The instance will sit for days in build/scheduling and never timeout or log an error.
logs found here http://paste.openstack.org/show/325841/