Instance status error after a nova boot. [closed]

asked 2016-01-19 07:44:12 -0500

anonymous user

Anonymous

updated 2016-01-21 01:42:33 -0500

Hi,

I have 4 nodes. one controller, with interface management in 10.0.0.1 one network, with interface management in 10.0.0.2, vm traffic in 10.0.1.2, and external in 172.17.x.x (the br-ex). two computes, with interfaces management in 10.0.0.3 and 10.0.0.4, and interfaces for vm traffic in 10.0.1.3 and 10.0.1.4.

I have deploy with packstack. i use vxlan and ovs. When i test to create VM, she got the error status.

In nova-compute.log : http://pastebin.com/4Z9hgSeK We can see binding fail. So it's the configuration neutron de probleme.

In openvswitch.log :

2016-01-19 14:51:35.680 2257 ERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor Interface name,ofport,external_ids --format=json]: None
2016-01-19 14:51:35.680 2257 ERROR neutron.agent.linux.async_process [-] Process [ovsdb-client monitor Interface name,ofport,external_ids --format=json] dies due to the error: None

my nova/neutron works fine : http://pastebin.com/ta3Wk7n1 ovs on network : http://pastebin.com/bhDBNsS2 and ovs in a compute node : http://pastebin.com/cbqngQEv

My external network :

   +-----------------+--------------------------------------+
    | Field           | Value                                |
    +-----------------+--------------------------------------+
    | admin_state_up  | True                                 |
    | id              | e5cbf4f6-1528-46fb-93b5-e64ce8f68564 |
    | mtu             | 0                                    |
    | name            | external                             |
    | router:external | True                                 |
    | shared          | True                                 |
    | status          | ACTIVE                               |
    | subnets         | e9b213aa-67d5-4f60-92c2-7220a3317dfd |
    | tenant_id       | services                             |
    +-----------------+--------------------------------------+

My subnet external network:

[root@controller ~(keystone_lucas)]# neutron subnet-list
+--------------------------------------+-----------------+----------------+--------------------------------------------------+
| id                                   | name            | cidr           | allocation_pools                                 |
+--------------------------------------+-----------------+----------------+--------------------------------------------------+
| e9b213aa-67d5-4f60-92c2-7220a3317dfd | external_subnet | 172.17.0.0/21  | {"start": "172.17.7.130", "end": "172.17.7.140"} |
| d6a61bcd-53b9-48ef-ad5b-36470cee01e0 | internal_subnet | 192.168.1.0/24 | {"start": "192.168.1.2", "end": "192.168.1.254"} |
+--------------------------------------+-----------------+----------------+--------------------------------------------------+

In my router, i have set a interface and a gateway.

[root@network ~(keystone_admin)]# ip netns exec qrouter-28b3ed16-86ad-40fd-9b1c-ca0c6cb2df65 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    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
10: qr-956d7bc9-59: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether fa:16:3e:ba:c4:27 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global qr-956d7bc9-59
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:feba:c427/64 scope link 
       valid_lft forever preferred_lft forever
11: qg-2b1a6363-ae: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether fa:16:3e:04:61:3f brd ff:ff:ff:ff:ff:ff
    inet 172.17.7.130/21 brd 172.17.7.255 scope global qg-2b1a6363-ae
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fe04:613f/64 scope link 
       valid_lft forever preferred_lft forever
[root@network ~(keystone_admin)]# ip netns exec qrouter-28b3ed16-86ad-40fd-9b1c-ca0c6cb2df65 ip r
default via 172.17.0.1 dev qg-2b1a6363-ae 
172.17.0.0/21 dev qg-2b1a6363-ae  proto kernel  scope link  src 172.17.7.130 
192.168.1.0/24 dev qr-956d7bc9-59  proto kernel  scope link  src 192.168.1.1 
[root@network ~(keystone_admin)]#

10 days than ... (more)

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Lucas LAMBOLEY
close date 2016-02-17 08:39:03.507907