系统集成instance获取不到ip

instance无法分配到ip

建议大家不要用openstack了，维护排错难，而且不稳定。无法找到日志报错相对应的解决办法。之前instance内部的ip可以正常获取的的，全都正常的。现在不知道为什么instance里面分配不到ip了。dashboard的in...显示全部

建议大家不要用openstack了，维护排错难，而且不稳定。无法找到日志报错相对应的解决办法。             之前instance内部的ip可以正常获取的的，全都正常的。现在不知道为什么instance里面分配不到ip了。dashboard的instance能看到分配的demo的ip和ext的ip。但是控制台的虚拟机里面分配不到ip。
   然后重启openvswitch的时候，计算节点的neutron日志报错了。日志在附件里，求助。附件里除了日志，还有每个节点的配置文件和mysql的dmp。

控制节点：
//在控制节点上ping 172.18.7.82，是能ping通的。
[root@controller ~]# neutron agent-list

+--------------------------------------+--------------------+-----------+-------+----------------+---------------------------+

| id                                  | agent_type       | host    | alive | admin_state_up | binary                   |

+--------------------------------------+--------------------+-----------+-------+----------------+---------------------------+

| 65363c71-ced1-4440-b22a-7a53edecb52f | Open vSwitch agent | network | :-) | True          | neutron-openvswitch-agent |

| 6fd21947-8995-4091-a1da-e9087e2e7bf8 | Open vSwitch agent | computer1 | :-) | True          | neutron-openvswitch-agent |

| 96cc19bd-9f6b-4168-9d82-152fa3e248ec | Metadata agent    | network | :-) | True          | neutron-metadata-agent |

| a36406cf-c18f-4aa2-8df1-337045e40855 | L3 agent          | network | :-) | True          | neutron-l3-agent       |

| f0d6cc74-c858-47de-a82c-9009fd065dd8 | DHCP agent       | network | :-) | True          | neutron-dhcp-agent       |

+--------------------------------------+--------------------+-----------+-------+----------------+---------------------------+

[root@controller ~]# neutron net-list

+--------------------------------------+----------+-----------------------------------------------------+

| id                                  | name    | subnets                                           |

+--------------------------------------+----------+-----------------------------------------------------+

| c6b49f01-5ab2-42ef-91bb-83e1306ee1ee | demo-net | 6ffb46e8-295b-4a16-a70e-068b46c1b781 192.168.1.0/24 |

| fdbbd1f5-8af9-494c-8736-317bb2656eae | ext-net  | a86410c8-0466-48ea-b300-1ab44e83b854 172.18.0.0/21  |

+--------------------------------------+----------+-----------------------------------------------------+

[root@controller ~]# neutron subnet-list

+--------------------------------------+-------------+----------------+--------------------------------------------------+

| id                                  | name       | cidr          | allocation_pools                               |

+--------------------------------------+-------------+----------------+--------------------------------------------------+

| 6ffb46e8-295b-4a16-a70e-068b46c1b781 | demo-subnet | 192.168.1.0/24 | {"start": "192.168.1.2", "end": "192.168.1.254"} |

| a86410c8-0466-48ea-b300-1ab44e83b854 | ext-subnet  | 172.18.0.0/21  | {"start": "172.18.7.80", "end": "172.18.7.99"} |

+--------------------------------------+-------------+----------------+--------------------------------------------------+

[root@controller ~]# neutron router-list

+--------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+

| id                                  | name       | external_gateway_info                                                                                                                                                                | distributed | ha |

+--------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+

| 7d9ae3d6-3314-44ce-a9db-87830ca0807d | demo-router | {"network_id": "fdbbd1f5-8af9-494c-8736-317bb2656eae", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "a86410c8-0466-48ea-b300-1ab44e83b854", "ip_address": "172.18.7.82"}]} | False    | False |

+--------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+

[root@controller ~]#

网络节点：
[root@network ~]# ip netns
qdhcp-c6b49f01-5ab2-42ef-91bb-83e1306ee1ee
qrouter-7d9ae3d6-3314-44ce-a9db-87830ca0807d

[root@network ~]# ip netns exec qdhcp-c6b49f01-5ab2-42ef-91bb-83e1306ee1ee ip addr
1: lo: 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

13: tapf0417184-b4: mtu 1500 qdisc noqueue state UNKNOWN

link/ether fa:16:3e:90:8e:49 brd ff:ff:ff:ff:ff:ff

inet 192.168.1.3/24 brd 192.168.1.255 scope global tapf0417184-b4

valid_lft forever preferred_lft forever

inet6 fe80::f816:3eff:fe90:8e49/64 scope link

valid_lft forever preferred_lft forever

[root@network ~]# ip netns exec qdhcp-c6b49f01-5ab2-42ef-91bb-83e1306ee1ee route

Kernel IP routing table

Destination    Gateway       Genmask       Flags Metric Ref Use Iface

default       192.168.1.1    0.0.0.0       UG 0    0       0 tapf0417184-b4

192.168.1.0    0.0.0.0       255.255.255.0 U    0    0       0 tapf0417184-b4

附件：

附件图标 openvswitch-agent.log (52.89 KB)

收起

关注1

参与12

查看其它 10 个回答jjqiu92的回答

jjqiu92系统工程师jjqiu

回复 8# AWCloud海云捷迅

[root@controller ~]# rabbitmqctl list_queues | grep -v '\<0$'
Listing queues ...
notifications.info    4
reply_b63dc4b79a384d2588f6cd573f6e89d2  2
reply_bf43796a2b7342faad9c3597a3783335  2
reply_dcc54f9c5036493b932cfc566b88d24a  4
reply_ee053addc29849e0aa68ec4dde847a73  2
reply_f3e5fe676cbc46c2a0b3773d2825858b  2
...done.

没有过量消息积压，而且我所有节点的所有服务重启过有6次了，看来不是mq消息积压的问题。主要是日志的那个报错不知道怎么解决。
[root@controller ~]# . /opt/demo-openrc.sh
[root@controller ~]# cat /etc/host
host.conf hostname    hosts       hosts.allow  hosts.deny
[root@controller ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1       localhost localhost.localdomain localhost6 localhost6.localdomain6
172.18.7.241 controller
172.18.7.245 computer1
172.18.7.246 network
172.18.7.244 storage1
172.18.7.242 storage2
[root@controller ~]# nova list
+--------------------------------------+----------------+--------+------------+-------------+-----------------------------------+
| ID                                  | Name          | Status | Task State | Power State | Networks                         |
+--------------------------------------+----------------+--------+------------+-------------+-----------------------------------+
| 2256ee85-eb5c-4e60-8c42-b6854129e7aa | demo-instance1 | ACTIVE | -       | Running    | demo-net=192.168.1.4, 172.18.7.84 |
| 415072a4-d6da-40cc-baa0-29056c926f98 | instance1    | ACTIVE | -       | Running    | demo-net=192.168.1.6             |
| 224cff91-067a-4c8c-a672-670c5bffee99 | test          | ACTIVE | -       | Running    | demo-net=192.168.1.5, 172.18.7.85 |
+--------------------------------------+----------------+--------+------------+-------------+-----------------------------------+

[root@computer1 ~]# tcpdump host 172.18.7.84
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp0s3, link-type EN10MB (Ethernet), capture size 65535 bytes

[root@network ~]# tcpdump host 172.18.7.84
tcpdump: WARNING: enp0s3: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp0s3, link-type EN10MB (Ethernet), capture size 65535 bytes

系统集成 · 2015-06-09

instance无法分配到ip

查看其它 10 个回答jjqiu92的回答

回答者

jjqiu92 最近回答过的问题

回答状态