Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

But how is the gateway device configured. Have you setup NAT or routing on
it so traffic can get back?

On Jun 13, 2017 4:07 AM, "xiaotie" <xiao...@ywe.cc> wrote:

> screenshot has eth0 up, but without IP address on it.
> I use following command to configure network:
> ifconfig eth0 192.168.5.204 netmask 255.255.255.0
> route add default gw 192.168.5.1
>
>
> 在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:
>
> -原始邮件-
> *发件人:* Kevin Benton <ke...@benton.pub>
> *发送时间:* 2017年6月13日 星期二
> *收件人:* xiaotie <xiao...@ywe.cc>
> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
> *主题:* Re: Re: Re: Re: Re: Re: [Openstack-operators] IP not been
> configured in VM os, but openstanck assign IP for it
>
> The screenshot in your other email didn't work. It's just a huge chunk of
> base64 data.
>
> How is 192.168.5.1 configured to perform routing?
>
> On Mon, Jun 12, 2017 at 8:09 PM, Kevin Benton <ke...@benton.pub> wrote:
>
>> Also, what did you mean by this sentence?
>>
>> "I relance an instance, but the problem is as before. how can i fix
>> this? There is no error in log file."
>>
>>
>> On Mon, Jun 12, 2017 at 7:47 PM, Kevin Benton <ke...@benton.pub> wrote:
>>
>>> I don't understand your topology now.  If 192.168.5.0/24 has a floating
>>> IP on it, that means it's an external network and that you have some other
>>> external router on it. What is the device at the gateway IP of the 
>>> 192.168.5.0
>>> network?
>>>
>>> On Mon, Jun 12, 2017 at 7:06 PM, xiaotie <xiao...@ywe.cc> wrote:
>>>
>>>> So sorry, use neutron port-show, I find 192.168.5.207 is floating IP.
>>>> dhcp IP is 192.168.5.200,it is pingable
>>>> You know 192.168.5.208 is my cloud vm ip address. It is automaticaly
>>>> configuer to vm os, I manually config it in the vm os. When I shutdown
>>>> network on the cloud vm, I use port-show to see 192.168.5.208's state, it
>>>> is the same as before.
>>>>
>>>> I relance an instance, but the problem is as before. how can i fix
>>>> this? There is no error in log file.
>>>>
>>>>
>>>> neutron port-show f24b534e-b1e3-4496-9dc0-b4408610b7de
>>>> neutron CLI is deprecated and will be removed in the future. Use
>>>> openstack CLI instead.
>>>> +---+---
>>>> ---+
>>>> | Field | Value
>>>>|
>>>> +---+---
>>>> ---+
>>>> | admin_state_up| True
>>>>|
>>>> | allowed_address_pairs |
>>>>  |
>>>> | binding:host_id   | controller
>>>>|
>>>> | binding:profile   | {}
>>>>|
>>>> | binding:vif_details   | {"port_filter": true}
>>>>|
>>>> | binding:vif_type  | bridge
>>>>|
>>>> | binding:vnic_type | normal
>>>>|
>>>> | created_at| 2017-06-11T05:40:32Z
>>>>|
>>>> | description   |
>>>>  |
>>>> | device_id | dhcpd3377d3c-a0d1-5d71-9947-f1
>>>> 7125c357bb-1807f022-b989-4725-9d25-7d176b28ec72|
>>>> | device_owner  | network:dhcp
>>>>|
>>>> | extra_dhcp_opts   |
>>>>  |
>>>> | fixed_ips | {"subnet_id": 
>>>> "59fc76f2-c666-4693-b0f6-2a96a0189ef7",
>>>> "ip_address": "192.168.5.200"} |
>>>> | id| f24b534e-b1e3-4496-9dc0-b44086
>>>> 10b7de |
>>>> | mac_address   | fa:16:3e:7a:0e:72

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[xiaotie]

screenshot has eth0 up, but without IP address on it.
I use following command to configure network:
ifconfig eth0 192.168.5.204 netmask 255.255.255.0
route add default gw 192.168.5.1


在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月13日 星期二
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: Re: Re: Re: Re: Re: [Openstack-operators] IP not been configured in VM 
os, but openstanck assign IP for it

The screenshot in your other email didn't work. It's just a huge chunk of 
base64 data.

How is 192.168.5.1 configured to perform routing?


On Mon, Jun 12, 2017 at 8:09 PM, Kevin Benton <ke...@benton.pub> wrote:
Also, what did you mean by this sentence?

"I relance an instance, but the problem is as before. how can i fix this? There 
is no error in log file."



On Mon, Jun 12, 2017 at 7:47 PM, Kevin Benton <ke...@benton.pub> wrote:
I don't understand your topology now.  If 192.168.5.0/24 has a floating IP on 
it, that means it's an external network and that you have some other external 
router on it. What is the device at the gateway IP of the 192.168.5.0 network? 

On Mon, Jun 12, 2017 at 7:06 PM, xiaotie <xiao...@ywe.cc> wrote:
So sorry, use neutron port-show, I find 192.168.5.207 is floating IP.
dhcp IP is 192.168.5.200,it is pingable
You know 192.168.5.208 is my cloud vm ip address. It is automaticaly configuer 
to vm os, I manually config it in the vm os. When I shutdown network on the 
cloud vm, I use port-show to see 192.168.5.208's state, it is the same as 
before.

I relance an instance, but the problem is as before. how can i fix this? There 
is no error in log file.


neutron port-show f24b534e-b1e3-4496-9dc0-b4408610b7de
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
+---+--+
| Field | Value 
   |
+---+--+
| admin_state_up| True  
   |
| allowed_address_pairs |   
   |
| binding:host_id   | controller
   |
| binding:profile   | {}
   |
| binding:vif_details   | {"port_filter": true} 
   |
| binding:vif_type  | bridge
   |
| binding:vnic_type | normal
   |
| created_at| 2017-06-11T05:40:32Z  
   |
| description   |   
   |
| device_id | 
dhcpd3377d3c-a0d1-5d71-9947-f17125c357bb-1807f022-b989-4725-9d25-7d176b28ec72   
 |
| device_owner  | network:dhcp  
   |
| extra_dhcp_opts   |   
   |
| fixed_ips | {"subnet_id": "59fc76f2-c666-4693-b0f6-2a96a0189ef7", 
"ip_address": "192.168.5.200"} |
| id| f24b534e-b1e3-4496-9dc0-b4408610b7de  
   |
| mac_address   | fa:16:3e:7a:0e:72 
   |
| name  |   
   |
| network_id| 1807f022-b989-4725-9d25-7d176b28ec72  
   |
| port_security_enabled | False 
   |
| project_id| 9ffad77b319f4025a7a048b8f358b047  
   |
| revision_number   | 25
   |
| security_groups   |   
   |
| status| ACTIVE
   |
| tags  |   
   |
| tenant_id | 9ffad77b319f4025a7a048b8f358b047

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

The screenshot in your other email didn't work. It's just a huge chunk of
base64 data.

How is 192.168.5.1 configured to perform routing?

On Mon, Jun 12, 2017 at 8:09 PM, Kevin Benton <ke...@benton.pub> wrote:

> Also, what did you mean by this sentence?
>
> "I relance an instance, but the problem is as before. how can i fix this?
> There is no error in log file."
>
>
> On Mon, Jun 12, 2017 at 7:47 PM, Kevin Benton <ke...@benton.pub> wrote:
>
>> I don't understand your topology now.  If 192.168.5.0/24 has a floating
>> IP on it, that means it's an external network and that you have some other
>> external router on it. What is the device at the gateway IP of the 
>> 192.168.5.0
>> network?
>>
>> On Mon, Jun 12, 2017 at 7:06 PM, xiaotie <xiao...@ywe.cc> wrote:
>>
>>> So sorry, use neutron port-show, I find 192.168.5.207 is floating IP.
>>> dhcp IP is 192.168.5.200,it is pingable
>>> You know 192.168.5.208 is my cloud vm ip address. It is automaticaly
>>> configuer to vm os, I manually config it in the vm os. When I shutdown
>>> network on the cloud vm, I use port-show to see 192.168.5.208's state, it
>>> is the same as before.
>>>
>>> I relance an instance, but the problem is as before. how can i fix this?
>>> There is no error in log file.
>>>
>>>
>>> neutron port-show f24b534e-b1e3-4496-9dc0-b4408610b7de
>>> neutron CLI is deprecated and will be removed in the future. Use
>>> openstack CLI instead.
>>> +---+---
>>> ---+
>>> | Field | Value
>>>|
>>> +---+---
>>> ---+
>>> | admin_state_up| True
>>>|
>>> | allowed_address_pairs |
>>>  |
>>> | binding:host_id   | controller
>>>|
>>> | binding:profile   | {}
>>>|
>>> | binding:vif_details   | {"port_filter": true}
>>>|
>>> | binding:vif_type  | bridge
>>>|
>>> | binding:vnic_type | normal
>>>|
>>> | created_at| 2017-06-11T05:40:32Z
>>>|
>>> | description   |
>>>  |
>>> | device_id | dhcpd3377d3c-a0d1-5d71-9947-f1
>>> 7125c357bb-1807f022-b989-4725-9d25-7d176b28ec72|
>>> | device_owner  | network:dhcp
>>>|
>>> | extra_dhcp_opts   |
>>>  |
>>> | fixed_ips | {"subnet_id": 
>>> "59fc76f2-c666-4693-b0f6-2a96a0189ef7",
>>> "ip_address": "192.168.5.200"} |
>>> | id| f24b534e-b1e3-4496-9dc0-b44086
>>> 10b7de |
>>> | mac_address   | fa:16:3e:7a:0e:72
>>>|
>>> | name  |
>>>  |
>>> | network_id| 1807f022-b989-4725-9d25-7d176b
>>> 28ec72 |
>>> | port_security_enabled | False
>>>|
>>> | project_id| 9ffad77b319f4025a7a048b8f358b0
>>> 47 |
>>> | revision_number   | 25
>>>|
>>> | security_groups   |
>>>  |
>>> | status| ACTIVE
>>>|
>>> | tags          |
>>>              |
>>> | tenant_id | 9ffad77b319f4025a7a048b8f358b0
>>> 47  

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

Also, what did you mean by this sentence?

"I relance an instance, but the problem is as before. how can i fix this?
There is no error in log file."


On Mon, Jun 12, 2017 at 7:47 PM, Kevin Benton <ke...@benton.pub> wrote:

> I don't understand your topology now.  If 192.168.5.0/24 has a floating
> IP on it, that means it's an external network and that you have some other
> external router on it. What is the device at the gateway IP of the 192.168.5.0
> network?
>
> On Mon, Jun 12, 2017 at 7:06 PM, xiaotie <xiao...@ywe.cc> wrote:
>
>> So sorry, use neutron port-show, I find 192.168.5.207 is floating IP.
>> dhcp IP is 192.168.5.200,it is pingable
>> You know 192.168.5.208 is my cloud vm ip address. It is automaticaly
>> configuer to vm os, I manually config it in the vm os. When I shutdown
>> network on the cloud vm, I use port-show to see 192.168.5.208's state, it
>> is the same as before.
>>
>> I relance an instance, but the problem is as before. how can i fix this?
>> There is no error in log file.
>>
>>
>> neutron port-show f24b534e-b1e3-4496-9dc0-b4408610b7de
>> neutron CLI is deprecated and will be removed in the future. Use
>> openstack CLI instead.
>> +---+---
>> ---+
>> | Field | Value
>>|
>> +---+---
>> ---+
>> | admin_state_up| True
>>|
>> | allowed_address_pairs |
>>  |
>> | binding:host_id   | controller
>>|
>> | binding:profile   | {}
>>|
>> | binding:vif_details   | {"port_filter": true}
>>|
>> | binding:vif_type  | bridge
>>|
>> | binding:vnic_type | normal
>>|
>> | created_at| 2017-06-11T05:40:32Z
>>|
>> | description   |
>>  |
>> | device_id | dhcpd3377d3c-a0d1-5d71-9947-f1
>> 7125c357bb-1807f022-b989-4725-9d25-7d176b28ec72|
>> | device_owner  | network:dhcp
>>|
>> | extra_dhcp_opts   |
>>  |
>> | fixed_ips | {"subnet_id": 
>> "59fc76f2-c666-4693-b0f6-2a96a0189ef7",
>> "ip_address": "192.168.5.200"} |
>> | id| f24b534e-b1e3-4496-9dc0-b44086
>> 10b7de |
>> | mac_address   | fa:16:3e:7a:0e:72
>>|
>> | name  |
>>  |
>> | network_id| 1807f022-b989-4725-9d25-7d176b
>> 28ec72 |
>> | port_security_enabled | False
>>|
>> | project_id| 9ffad77b319f4025a7a048b8f358b0
>> 47 |
>> | revision_number   | 25
>>|
>> | security_groups   |
>>  |
>> | status| ACTIVE
>>|
>> | tags  |
>>  |
>> | tenant_id | 9ffad77b319f4025a7a048b8f358b0
>> 47 |
>> | updated_at        | 2017-06-12T21:23:08Z
>>        |
>> +---+---
>> ---+
>>
>>
>> 在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:
>>
>> -原始邮件-
>> *发件人:* Kevin Benton <ke...@benton.pub>
>> *发送时间:* 2017年6月13日 星期二
>> *收件人:* xiaotie <xiao...@ywe.cc>
>> *抄送:* O

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

If you're booting a VM directly on the provider network, then you don't
need to worry about the openstack router. It should be able to ping
192.168.5.1 directly and get outside of the network that way.

On Mon, Jun 12, 2017 at 8:04 PM, xiaotie <xiao...@ywe.cc> wrote:

> I use vituralbox on mac pro, I user two vm on vitualbox to set up
> openstack.
> Each vm has two ethernet:
>  one is use bridge on en0 wifi, which local net is 192.168.5.0/24
> ，its gateway ip is 192.168.5.1。I use it to simulate provider network
>  the other nat network，which net is 10.0.2.0/24 . I use it to
> simulate the self-service network
>
> openstack router ip is 192.168.5.203, and the ip range I assign to
> openstack is 192.168.5.200 -- 192.168.5.250
>
> Is this information is enough?
>
> 在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:
>
> -原始邮件-
> *发件人:* Kevin Benton <ke...@benton.pub>
> *发送时间:* 2017年6月13日 星期二
> *收件人:* xiaotie <xiao...@ywe.cc>
> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
> *主题:* Re: Re: Re: Re: Re: Re: [Openstack-operators] IP not been
> configured in VM os, but openstanck assign IP for it
>
>
> I don't understand your topology now.  If 192.168.5.0/24 has a floating
> IP on it, that means it's an external network and that you have some other
> external router on it. What is the device at the gateway IP of the 192.168.5.0
> network?
>
> On Mon, Jun 12, 2017 at 7:06 PM, xiaotie <xiao...@ywe.cc> wrote:
>
>> So sorry, use neutron port-show, I find 192.168.5.207 is floating IP.
>> dhcp IP is 192.168.5.200,it is pingable
>> You know 192.168.5.208 is my cloud vm ip address. It is automaticaly
>> configuer to vm os, I manually config it in the vm os. When I shutdown
>> network on the cloud vm, I use port-show to see 192.168.5.208's state, it
>> is the same as before.
>>
>> I relance an instance, but the problem is as before. how can i fix this?
>> There is no error in log file.
>>
>>
>> neutron port-show f24b534e-b1e3-4496-9dc0-b4408610b7de
>> neutron CLI is deprecated and will be removed in the future. Use
>> openstack CLI instead.
>> +---+---
>> ---+
>> | Field | Value
>>|
>> +---+---
>> ---+
>> | admin_state_up| True
>>|
>> | allowed_address_pairs |
>>  |
>> | binding:host_id   | controller
>>|
>> | binding:profile   | {}
>>|
>> | binding:vif_details   | {"port_filter": true}
>>|
>> | binding:vif_type  | bridge
>>|
>> | binding:vnic_type | normal
>>|
>> | created_at| 2017-06-11T05:40:32Z
>>|
>> | description   |
>>  |
>> | device_id | dhcpd3377d3c-a0d1-5d71-9947-f1
>> 7125c357bb-1807f022-b989-4725-9d25-7d176b28ec72|
>> | device_owner  | network:dhcp
>>|
>> | extra_dhcp_opts   |
>>  |
>> | fixed_ips | {"subnet_id": 
>> "59fc76f2-c666-4693-b0f6-2a96a0189ef7",
>> "ip_address": "192.168.5.200"} |
>> | id| f24b534e-b1e3-4496-9dc0-b44086
>> 10b7de |
>> | mac_address   | fa:16:3e:7a:0e:72
>>|
>> | name  |
>>  |
>> | network_id| 1807f022-b989-4725-9d25-7d176b
>> 28ec72 |
>> | port_security_enabled | False
>>|
>> | project_id| 9ffad77b319f4025a7a048b8f358b0
>> 47 |
>&g

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[xiaotie]

-o1ed7d417-3  all  --  0.0.0.0/00.0.0.0/0   
 PHYSDEV match --physdev-in tap1ed7d417-30 --physdev-is-bridged /* Jump to the 
VM specific chain. */
neutron-linuxbri-id1b662c1-6  all  --  0.0.0.0/00.0.0.0/0   
 PHYSDEV match --physdev-out tapd1b662c1-67 --physdev-is-bridged /* Jump to the 
VM specific chain. */
neutron-linuxbri-od1b662c1-6  all  --  0.0.0.0/00.0.0.0/0   
 PHYSDEV match --physdev-in tapd1b662c1-67 --physdev-is-bridged /* Jump to the 
VM specific chain. */
ACCEPT all  --  0.0.0.0/00.0.0.0/0

Chain neutron-linuxbri-sg-fallback (4 references)
target prot opt source   destination
DROP   all  --  0.0.0.0/00.0.0.0/0/* Default drop 
rule for unmatched traffic. */

Chain nova-compute-FORWARD (1 references)
target prot opt source   destination
ACCEPT all  --  0.0.0.0/00.0.0.0/0
ACCEPT all  --  0.0.0.0/00.0.0.0/0
DROP   all  --  0.0.0.0/00.0.0.0/0

Chain nova-compute-INPUT (1 references)
target prot opt source   destination

Chain nova-compute-OUTPUT (1 references)
target prot opt source   destination

Chain nova-compute-local (1 references)
target prot opt source   destination

Chain nova-filter-top (2 references)
target prot opt source   destination
nova-compute-local  all  --  0.0.0.0/00.0.0.0/0


在2017-06-13，xiaotie <xiao...@ywe.cc> 写道:-原始邮件-
 发件人: xiaotie <xiao...@ywe.cc>
 发送时间: 2017年6月13日 星期二
 收件人: Kevin Benton <ke...@benton.pub>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re:Re: Re: Re: Re: Re: Re: [Openstack-operators] IP not been configured in 
VM os, but openstanck assign IP for it

I use vituralbox on mac pro, I user two vm on vitualbox to set up openstack.
Each vm has two ethernet:
 one is use bridge on en0 wifi, which local net is 192.168.5.0/24 ，its 
gateway ip is 192.168.5.1。I use it to simulate provider network
 the other nat network，which net is 10.0.2.0/24 . I use it to simulate the 
self-service network

openstack router ip is 192.168.5.203, and the ip range I assign to openstack is 
192.168.5.200 -- 192.168.5.250

Is this information is enough?

在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月13日 星期二
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: Re: Re: Re: Re: Re: [Openstack-operators] IP not been configured in VM 
os, but openstanck assign IP for it

I don't understand your topology now.  If 192.168.5.0/24 has a floating IP on 
it, that means it's an external network and that you have some other external 
router on it. What is the device at the gateway IP of the 192.168.5.0 network? 

On Mon, Jun 12, 2017 at 7:06 PM, xiaotie <xiao...@ywe.cc> wrote:
So sorry, use neutron port-show, I find 192.168.5.207 is floating IP.
dhcp IP is 192.168.5.200,it is pingable
You know 192.168.5.208 is my cloud vm ip address. It is automaticaly configuer 
to vm os, I manually config it in the vm os. When I shutdown network on the 
cloud vm, I use port-show to see 192.168.5.208's state, it is the same as 
before.

I relance an instance, but the problem is as before. how can i fix this? There 
is no error in log file.


neutron port-show f24b534e-b1e3-4496-9dc0-b4408610b7de
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
+---+--+
| Field | Value 
   |
+---+--+
| admin_state_up| True  
   |
| allowed_address_pairs |   
   |
| binding:host_id   | controller
   |
| binding:profile   | {}
   |
| binding:vif_details   | {"port_filter": true} 
   |
| binding:vif_type  | bridge
   |
| binding:vnic_type | normal
   |
| created_at| 2017-06-11T05:40:32Z  
   |
| description   |   
   |
| device_id  

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[xiaotie]

I use vituralbox on mac pro, I user two vm on vitualbox to set up openstack.
Each vm has two ethernet:
 one is use bridge on en0 wifi, which local net is 192.168.5.0/24 ，its 
gateway ip is 192.168.5.1。I use it to simulate provider network
 the other nat network，which net is 10.0.2.0/24 . I use it to simulate the 
self-service network

openstack router ip is 192.168.5.203, and the ip range I assign to openstack is 
192.168.5.200 -- 192.168.5.250

Is this information is enough?

在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月13日 星期二
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: Re: Re: Re: Re: Re: [Openstack-operators] IP not been configured in VM 
os, but openstanck assign IP for it

I don't understand your topology now.  If 192.168.5.0/24 has a floating IP on 
it, that means it's an external network and that you have some other external 
router on it. What is the device at the gateway IP of the 192.168.5.0 network? 

On Mon, Jun 12, 2017 at 7:06 PM, xiaotie <xiao...@ywe.cc> wrote:
So sorry, use neutron port-show, I find 192.168.5.207 is floating IP.
dhcp IP is 192.168.5.200,it is pingable
You know 192.168.5.208 is my cloud vm ip address. It is automaticaly configuer 
to vm os, I manually config it in the vm os. When I shutdown network on the 
cloud vm, I use port-show to see 192.168.5.208's state, it is the same as 
before.

I relance an instance, but the problem is as before. how can i fix this? There 
is no error in log file.


neutron port-show f24b534e-b1e3-4496-9dc0-b4408610b7de
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
+---+--+
| Field | Value 
   |
+---+--+
| admin_state_up| True  
   |
| allowed_address_pairs |   
   |
| binding:host_id   | controller
   |
| binding:profile   | {}
   |
| binding:vif_details   | {"port_filter": true} 
   |
| binding:vif_type  | bridge
   |
| binding:vnic_type | normal
   |
| created_at| 2017-06-11T05:40:32Z  
   |
| description   |   
   |
| device_id | 
dhcpd3377d3c-a0d1-5d71-9947-f17125c357bb-1807f022-b989-4725-9d25-7d176b28ec72   
 |
| device_owner  | network:dhcp  
   |
| extra_dhcp_opts   |   
   |
| fixed_ips | {"subnet_id": "59fc76f2-c666-4693-b0f6-2a96a0189ef7", 
"ip_address": "192.168.5.200"} |
| id| f24b534e-b1e3-4496-9dc0-b4408610b7de  
   |
| mac_address   | fa:16:3e:7a:0e:72 
   |
| name  |   
   |
| network_id| 1807f022-b989-4725-9d25-7d176b28ec72  
   |
| port_security_enabled | False 
   |
| project_id| 9ffad77b319f4025a7a048b8f358b047  
   |
| revision_number   | 25
   |
| security_groups   |   
   |
| status| ACTIVE
   |
| tags  |   
   |
| tenant_id | 9ffad77b319f4025a7a048b8f358b047  

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

I don't understand your topology now.  If 192.168.5.0/24 has a floating IP
on it, that means it's an external network and that you have some other
external router on it. What is the device at the gateway IP of the 192.168.5.0
network?

On Mon, Jun 12, 2017 at 7:06 PM, xiaotie <xiao...@ywe.cc> wrote:

> So sorry, use neutron port-show, I find 192.168.5.207 is floating IP.
> dhcp IP is 192.168.5.200,it is pingable
> You know 192.168.5.208 is my cloud vm ip address. It is automaticaly
> configuer to vm os, I manually config it in the vm os. When I shutdown
> network on the cloud vm, I use port-show to see 192.168.5.208's state, it
> is the same as before.
>
> I relance an instance, but the problem is as before. how can i fix this?
> There is no error in log file.
>
>
> neutron port-show f24b534e-b1e3-4496-9dc0-b4408610b7de
> neutron CLI is deprecated and will be removed in the future. Use openstack
> CLI instead.
> +---+---
> ---+
> | Field | Value
>|
> +---+---
> ---+
> | admin_state_up| True
>|
> | allowed_address_pairs |
>  |
> | binding:host_id   | controller
>|
> | binding:profile   | {}
>|
> | binding:vif_details   | {"port_filter": true}
>|
> | binding:vif_type  | bridge
>|
> | binding:vnic_type | normal
>|
> | created_at| 2017-06-11T05:40:32Z
>|
> | description   |
>  |
> | device_id | dhcpd3377d3c-a0d1-5d71-9947-
> f17125c357bb-1807f022-b989-4725-9d25-7d176b28ec72|
> | device_owner  | network:dhcp
>|
> | extra_dhcp_opts   |
>  |
> | fixed_ips | {"subnet_id": 
> "59fc76f2-c666-4693-b0f6-2a96a0189ef7",
> "ip_address": "192.168.5.200"} |
> | id| f24b534e-b1e3-4496-9dc0-
> b4408610b7de |
> | mac_address   | fa:16:3e:7a:0e:72
>|
> | name  |
>  |
> | network_id| 1807f022-b989-4725-9d25-
> 7d176b28ec72 |
> | port_security_enabled | False
>|
> | project_id| 9ffad77b319f4025a7a048b8f358b0
> 47 |
> | revision_number   | 25
>|
> | security_groups   |
>  |
> | status| ACTIVE
>|
> | tags  |
>  |
> | tenant_id | 9ffad77b319f4025a7a048b8f358b0
> 47 |
> | updated_at| 2017-06-12T21:23:08Z
>|
> +---+---
> ---+
>
>
> 在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:
>
> -原始邮件-
> *发件人:* Kevin Benton <ke...@benton.pub>
> *发送时间:* 2017年6月13日 星期二
> *收件人:* xiaotie <xiao...@ywe.cc>
> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
> *主题:* Re: Re: Re: Re: Re: [Openstack-operators] IP not been configured in
> VM os, but openstanck assign IP for it
>
>
> Name is just a field that can be set by users to track things.
>
> Do a neutron port-show on e949854e-3533-48c5-8a1a-3dc455dfa59c to see the
> details of that DHCP agent port.
>
> On Mon, Jun 12, 2017 at 5:53 PM, xiaotie <xiao...@ywe.cc> wrote:
>
>> its result is
>> [root@controller neutron]# neutron port-list
>> neutron CLI is deprecated and will be 

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[xiaotie]

So sorry, use neutron port-show, I find 192.168.5.207 is floating IP.
dhcp IP is 192.168.5.200,it is pingable
You know 192.168.5.208 is my cloud vm ip address. It is automaticaly configuer 
to vm os, I manually config it in the vm os. When I shutdown network on the 
cloud vm, I use port-show to see 192.168.5.208's state, it is the same as 
before.

I relance an instance, but the problem is as before. how can i fix this? There 
is no error in log file.


neutron port-show f24b534e-b1e3-4496-9dc0-b4408610b7de
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
+---+--+
| Field | Value 
   |
+---+--+
| admin_state_up| True  
   |
| allowed_address_pairs |   
   |
| binding:host_id   | controller
   |
| binding:profile   | {}
   |
| binding:vif_details   | {"port_filter": true} 
   |
| binding:vif_type  | bridge
   |
| binding:vnic_type | normal
   |
| created_at| 2017-06-11T05:40:32Z  
   |
| description   |   
   |
| device_id | 
dhcpd3377d3c-a0d1-5d71-9947-f17125c357bb-1807f022-b989-4725-9d25-7d176b28ec72   
 |
| device_owner  | network:dhcp  
   |
| extra_dhcp_opts   |   
   |
| fixed_ips | {"subnet_id": "59fc76f2-c666-4693-b0f6-2a96a0189ef7", 
"ip_address": "192.168.5.200"} |
| id| f24b534e-b1e3-4496-9dc0-b4408610b7de  
   |
| mac_address   | fa:16:3e:7a:0e:72 
   |
| name  |   
   |
| network_id| 1807f022-b989-4725-9d25-7d176b28ec72  
   |
| port_security_enabled | False 
   |
| project_id| 9ffad77b319f4025a7a048b8f358b047  
   |
| revision_number   | 25
   |
| security_groups   |   
   |
| status| ACTIVE
   |
| tags  |   
   |
| tenant_id | 9ffad77b319f4025a7a048b8f358b047  
   |
| updated_at| 2017-06-12T21:23:08Z  
   |
+---+--+


在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月13日 星期二
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: Re: Re: Re: Re: [Openstack-operators] IP not been configured in VM os, 
but openstanck assign IP for it

Name is just a field that can be set by users to track things.

Do a neutron port-show on e949854e-3533-48c5-8a1a-3dc455dfa59c to see the 
details of that DHCP agent port.


On Mon, Jun 12, 2017 at 5:53 PM, xiaotie <xiao...@ywe.cc> wrote:
its result is
 [root@controller neutron]# neutron port-list
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
+--+--+--+---+--+
| id 

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

Name is just a field that can be set by users to track things.

Do a neutron port-show on e949854e-3533-48c5-8a1a-3dc455dfa59c to see the
details of that DHCP agent port.

On Mon, Jun 12, 2017 at 5:53 PM, xiaotie <xiao...@ywe.cc> wrote:

> its result is
> [root@controller neutron]# neutron port-list
> neutron CLI is deprecated and will be removed in the future. Use openstack
> CLI instead.
> +--+--+-
> -+---+--
> +
> | id   | name |
> tenant_id| mac_address   |
> fixed_ips
> |
> +--+--+-
> -+---+--
> +
> | 40b6d8da-01a9-41ab-a48f-a7b00185853e |  |
> dfeb844b4942417e9e2d1299c49d1a3a | fa:16:3e:59:91:c0 | {"subnet_id":
> "f12e2ca7-133e-4b46-ad9b-8784d509eb0a", "ip_address": "172.16.1.1"}|
> | 793528db-e2c5-4b39-8f18-246362dd4a03 |
> |  | fa:16:3e:43:03:a0 | {"subnet_id":
> "59fc76f2-c666-4693-b0f6-2a96a0189ef7", "ip_address": "192.168.5.203"} |
> | e949854e-3533-48c5-8a1a-3dc455dfa59c |
> |  | fa:16:3e:c6:0a:ff | {"subnet_id":
> "59fc76f2-c666-4693-b0f6-2a96a0189ef7", "ip_address": "192.168.5.207"} |
> | f24b534e-b1e3-4496-9dc0-b4408610b7de |  |
> 9ffad77b319f4025a7a048b8f358b047 | fa:16:3e:7a:0e:72 | {"subnet_id":
> "59fc76f2-c666-4693-b0f6-2a96a0189ef7", "ip_address": "192.168.5.200"} |
> | f74ad12c-0134-4a33-bf32-e6dd12535673 |  |
> dfeb844b4942417e9e2d1299c49d1a3a | fa:16:3e:ac:45:41 | {"subnet_id":
> "f12e2ca7-133e-4b46-ad9b-8784d509eb0a", "ip_address": "172.16.1.2"}|
> | ffac71c1-cda8-4431-896c-a0e48515ea8f |  |
> dfeb844b4942417e9e2d1299c49d1a3a | fa:16:3e:63:8b:26 | {"subnet_id":
> "59fc76f2-c666-4693-b0f6-2a96a0189ef7", "ip_address": "192.168.5.208"} |
> +--+--+-
> -+---+--
> +
>
> 192.168.5.200 is provider network's start IP,192.168.5.203 is router IP,
> 192.168.5.208 is openstack vm instance IP, I configure it in vm os
> manually, they can ping from controller;
> may be 192.168.5.207 is dhcp agent IP, I can't confirm this , and can't
> ping.
>
> 172.16 is self-service network
>
> Why name field has no value? if 5.207 is dhcp agent ip and is not
> pingable, is this the root cause? how can i fix this
>
>
> 在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:
>
> -原始邮件-
> *发件人:* Kevin Benton <ke...@benton.pub>
> *发送时间:* 2017年6月13日 星期二
> *收件人:* xiaotie <xiao...@ywe.cc>
> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
> *主题:* Re: Re: Re: Re: [Openstack-operators] IP not been configured in VM
> os, but openstanck assign IP for it
>
>
> If you do a 'neutron port-list' do you see the DHCP agent port and is it
> ACTIVE?
>
> On Mon, Jun 12, 2017 at 3:19 PM, xiaotie <xiao...@ywe.cc> wrote:
>
>> Is your mean as follow:
>> [root@controller ~]# neutron agent-list
>> neutron CLI is deprecated and will be removed in the future. Use
>> openstack CLI instead.
>> +--+
>> ++---+---++-
>> --+
>> | id   | agent_type | host
>> | availability_zone | alive | admin_state_up | binary|
>> +--+
>> ++---+---++-
>> --+
>> | 214ea02c-ee30-4b0d-850e-09a78040531d | Linux bridge agent | controller
>> |   | :-)   | True   | neutron-linuxbridge-agent |
>> | 3a72b736-91b9-40d0-a202-265417760d7d | L3 agent   | controller
>> | nova  | :-)   | True   | neutron-l3-agent  |
>> | 42ca2ff4-ec58-4a38-afef-6a728347b3e6 | Metadata agent | controller
>> |   | :-)   | True   | neutron-metadata-agent|
>> | 82b060a1-94bd-4d03-a39f-894f251a9557 | Linux bridge agent | compute01
>> |

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[xiaotie]

its result is
 [root@controller neutron]# neutron port-list
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
+--+--+--+---+--+
| id   | name | tenant_id   
 | mac_address   | fixed_ips
|
+--+--+--+---+--+
| 40b6d8da-01a9-41ab-a48f-a7b00185853e |  | 
dfeb844b4942417e9e2d1299c49d1a3a | fa:16:3e:59:91:c0 | {"subnet_id": 
"f12e2ca7-133e-4b46-ad9b-8784d509eb0a", "ip_address": "172.16.1.1"}|
| 793528db-e2c5-4b39-8f18-246362dd4a03 |  | 
 | fa:16:3e:43:03:a0 | {"subnet_id": "59fc76f2-c666-4693-b0f6-2a96a0189ef7", 
"ip_address": "192.168.5.203"} |
| e949854e-3533-48c5-8a1a-3dc455dfa59c |  | 
 | fa:16:3e:c6:0a:ff | {"subnet_id": "59fc76f2-c666-4693-b0f6-2a96a0189ef7", 
"ip_address": "192.168.5.207"} |
| f24b534e-b1e3-4496-9dc0-b4408610b7de |  | 
9ffad77b319f4025a7a048b8f358b047 | fa:16:3e:7a:0e:72 | {"subnet_id": 
"59fc76f2-c666-4693-b0f6-2a96a0189ef7", "ip_address": "192.168.5.200"} |
| f74ad12c-0134-4a33-bf32-e6dd12535673 |  | 
dfeb844b4942417e9e2d1299c49d1a3a | fa:16:3e:ac:45:41 | {"subnet_id": 
"f12e2ca7-133e-4b46-ad9b-8784d509eb0a", "ip_address": "172.16.1.2"}|
| ffac71c1-cda8-4431-896c-a0e48515ea8f |  | 
dfeb844b4942417e9e2d1299c49d1a3a | fa:16:3e:63:8b:26 | {"subnet_id": 
"59fc76f2-c666-4693-b0f6-2a96a0189ef7", "ip_address": "192.168.5.208"} |
+--+--+--+---+--+

192.168.5.200 is provider network's start IP,192.168.5.203 is router IP, 
192.168.5.208 is openstack vm instance IP, I configure it in vm os manually, 
they can ping from controller;
may be 192.168.5.207 is dhcp agent IP, I can't confirm this , and can't ping.

172.16 is self-service network

Why name field has no value? if 5.207 is dhcp agent ip and is not pingable, is 
this the root cause? how can i fix this


在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月13日 星期二
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: Re: Re: Re: [Openstack-operators] IP not been configured in VM os, but 
openstanck assign IP for it

If you do a 'neutron port-list' do you see the DHCP agent port and is it ACTIVE?

On Mon, Jun 12, 2017 at 3:19 PM, xiaotie <xiao...@ywe.cc> wrote:
Is your mean as follow:
[root@controller ~]# neutron agent-list
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
+--+++---+---++---+
| id   | agent_type | host   | 
availability_zone | alive | admin_state_up | binary|
+--+++---+---++---+
| 214ea02c-ee30-4b0d-850e-09a78040531d | Linux bridge agent | controller |  
 | :-)   | True   | neutron-linuxbridge-agent |
| 3a72b736-91b9-40d0-a202-265417760d7d | L3 agent   | controller | nova 
 | :-)   | True   | neutron-l3-agent  |
| 42ca2ff4-ec58-4a38-afef-6a728347b3e6 | Metadata agent | controller |  
 | :-)   | True   | neutron-metadata-agent|
| 82b060a1-94bd-4d03-a39f-894f251a9557 | Linux bridge agent | compute01  |  
 | :-)   | True   | neutron-linuxbridge-agent |
| 99e9f7f8-1823-416a-ab09-987f88ce1b2c | DHCP agent | controller | nova 
 | :-)   | True   | neutron-dhcp-agent|
+--+++---+---++---+

I run dhcp agent on the controller, as the quick install doc suggest artechure. 
and I can see some port as follow
[root@controller ~]# netstat -tunlp | grep dh
udp0  0 0.0.0.0:68  0.0.0.0:*   
696/dhclient
udp0   

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

If you do a 'neutron port-list' do you see the DHCP agent port and is it
ACTIVE?

On Mon, Jun 12, 2017 at 3:19 PM, xiaotie <xiao...@ywe.cc> wrote:

> Is your mean as follow:
> [root@controller ~]# neutron agent-list
> neutron CLI is deprecated and will be removed in the future. Use openstack
> CLI instead.
> +--+
> ++---+---++-
> --+
> | id   | agent_type | host
> | availability_zone | alive | admin_state_up | binary|
> +--+
> ++---+---++-
> --+
> | 214ea02c-ee30-4b0d-850e-09a78040531d | Linux bridge agent | controller
> |   | :-)   | True   | neutron-linuxbridge-agent |
> | 3a72b736-91b9-40d0-a202-265417760d7d | L3 agent   | controller
> | nova  | :-)   | True   | neutron-l3-agent  |
> | 42ca2ff4-ec58-4a38-afef-6a728347b3e6 | Metadata agent | controller
> |   | :-)   | True   | neutron-metadata-agent|
> | 82b060a1-94bd-4d03-a39f-894f251a9557 | Linux bridge agent | compute01
> |   | :-)   | True   | neutron-linuxbridge-agent |
> | 99e9f7f8-1823-416a-ab09-987f88ce1b2c | DHCP agent | controller
> | nova  | :-)   | True   | neutron-dhcp-agent|
> +--+
> ++---+---++-
> --+
>
> I run dhcp agent on the controller, as the quick install doc suggest
> artechure. and I can see some port as follow
> [root@controller ~]# netstat -tunlp | grep dh
> udp0  0 0.0.0.0:68  0.0.0.0:*
> 696/dhclient
> udp0  0 0.0.0.0:44070.0.0.0:*
> 696/dhclient
> udp6   0  0 :::21133:::*
> 696/dhclient
>
> you mean: I lanch another vm not on openstack platform, set its ethernet
> proto to dhcp?
>
>
> 在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:
>
> -原始邮件-
> *发件人:* Kevin Benton <ke...@benton.pub>
> *发送时间:* 2017年6月13日 星期二
> *收件人:* xiaotie <xiao...@ywe.cc>
> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
> *主题:* Re: Re: Re: [Openstack-operators] IP not been configured in VM os,
> but openstanck assign IP for it
>
>
> You need to run the DHCP agent on either the compute node or the same node
> running the L3 agent. It will get a port on the same network and offer DHCP
> addresses to the devices on that network.
>
> On Mon, Jun 12, 2017 at 3:09 PM, xiaotie <xiao...@ywe.cc> wrote:
>
>> Thank you kevin.
>> I just edit neutone code file and log nosise disapper.
>>
>> As you say, the vm does not automate be configured ip address. But when I
>> configure the address that openstack assign to it in the vm os, I can ping
>> local network,but I can't
>> ping 8.8.8.8. On my physical server in the same local network , I can
>> ping 8.8.8.8
>>
>> And another tiny question, how can I get dhcp address, and can you give
>> me some advice about which doc I can get experiencd with openstack's common
>> command and case.
>>
>>
>> 在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:
>>
>> -原始邮件-
>> *发件人:* Kevin Benton <ke...@benton.pub>
>> *发送时间:* 2017年6月13日 星期二
>> *收件人:* xiaotie <xiao...@ywe.cc>
>> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
>> *主题:* Re: Re: [Openstack-operators] IP not been configured in VM os, but
>> openstanck assign IP for it
>>
>>
>> That bug just fixes the log noise. That was not the cause of the failure.
>>
>> Check my suggestion about confirming that DHCP is working.
>>
>> On Mon, Jun 12, 2017 at 4:11 AM, xiaotie <xiao...@ywe.cc> wrote:
>>
>>> hi,kevin
>>> From this link， I think you have fix this bug. But how can I use it in
>>> my environment?
>>> Please forgive me, I'm newbie to openstack.
>>> In my environment, I use centos7.3, and use yum to install openstack.
>>>
>>> 在2017-06-12，Kevin Benton <ke...@benton.pub> 写道:
>>>
>>> -原始邮件-
>>> *发件人:* Kevin Benton <ke...@benton.pub>
>>> *发送时间:* 2017年6月12日 星期一
>>> *收件人:* xiaotie <xiao...@ywe.cc>
>>> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
>>> *主题:* Re: [Openstack-operators] IP not b

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[xiaotie]

Is your mean as follow:
[root@controller ~]# neutron agent-list
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
+--+++---+---++---+
| id   | agent_type | host   | 
availability_zone | alive | admin_state_up | binary|
+--+++---+---++---+
| 214ea02c-ee30-4b0d-850e-09a78040531d | Linux bridge agent | controller |  
 | :-)   | True   | neutron-linuxbridge-agent |
| 3a72b736-91b9-40d0-a202-265417760d7d | L3 agent   | controller | nova 
 | :-)   | True   | neutron-l3-agent  |
| 42ca2ff4-ec58-4a38-afef-6a728347b3e6 | Metadata agent | controller |  
 | :-)   | True   | neutron-metadata-agent|
| 82b060a1-94bd-4d03-a39f-894f251a9557 | Linux bridge agent | compute01  |  
 | :-)   | True   | neutron-linuxbridge-agent |
| 99e9f7f8-1823-416a-ab09-987f88ce1b2c | DHCP agent | controller | nova 
 | :-)   | True   | neutron-dhcp-agent|
+--+++---+---++---+

I run dhcp agent on the controller, as the quick install doc suggest artechure. 
and I can see some port as follow
[root@controller ~]# netstat -tunlp | grep dh
udp0  0 0.0.0.0:68  0.0.0.0:*   
696/dhclient
udp0  0 0.0.0.0:44070.0.0.0:*   
696/dhclient
udp6   0  0 :::21133:::*
696/dhclient

you mean: I lanch another vm not on openstack platform, set its ethernet proto 
to dhcp?


在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月13日 星期二
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: Re: Re: [Openstack-operators] IP not been configured in VM os, but 
openstanck assign IP for it

You need to run the DHCP agent on either the compute node or the same node 
running the L3 agent. It will get a port on the same network and offer DHCP 
addresses to the devices on that network.

On Mon, Jun 12, 2017 at 3:09 PM, xiaotie <xiao...@ywe.cc> wrote:
Thank you kevin.
I just edit neutone code file and log nosise disapper.

As you say, the vm does not automate be configured ip address. But when I 
configure the address that openstack assign to it in the vm os, I can ping 
local network,but I can't
ping 8.8.8.8. On my physical server in the same local network , I can ping 
8.8.8.8

And another tiny question, how can I get dhcp address, and can you give me some 
advice about which doc I can get experiencd with openstack's common command and 
case.


在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月13日 星期二
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: Re: [Openstack-operators] IP not been configured in VM os, but 
openstanck assign IP for it

That bug just fixes the log noise. That was not the cause of the failure.

Check my suggestion about confirming that DHCP is working.

On Mon, Jun 12, 2017 at 4:11 AM, xiaotie <xiao...@ywe.cc> wrote:
hi,kevin
From this link， I think you have fix this bug. But how can I use it in my 
environment?
Please forgive me, I'm newbie to openstack.
In my environment, I use centos7.3, and use yum to install openstack.

 在2017-06-12，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月12日 星期一
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: [Openstack-operators] IP not been configured in VM os, but openstanck 
assign IP for it

I believe that error is actually unrelated (bug reported here for that 
https://bugs.launchpad.net/neutron/+bug/1697383 ).


Do you have the DHCP agent running and is it's port active on the network? You 
should be able to ping the DHCP address from the 192.168.5 network.


If you don't have the DHCP agent, you will need to manually assign the IP in 
your instance.


On Sun, Jun 11, 2017 at 11:40 PM, xiaotie <xiao...@ywe.cc> wrote:

I lanch an instance, but the instance has not IP when I run command
  'ip addr'.But router has assign ip for it.

  My environment is:
  two vms in virtualbox
  each vm has two ethernet, 192.168.5.0/24 use bridge network; 10.0.0.0/24 use 
nat network, both is ok
  I lanch provider network, and 

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

You need to run the DHCP agent on either the compute node or the same node
running the L3 agent. It will get a port on the same network and offer DHCP
addresses to the devices on that network.

On Mon, Jun 12, 2017 at 3:09 PM, xiaotie <xiao...@ywe.cc> wrote:

> Thank you kevin.
> I just edit neutone code file and log nosise disapper.
>
> As you say, the vm does not automate be configured ip address. But when I
> configure the address that openstack assign to it in the vm os, I can ping
> local network,but I can't
> ping 8.8.8.8. On my physical server in the same local network , I can ping
> 8.8.8.8
>
> And another tiny question, how can I get dhcp address, and can you give me
> some advice about which doc I can get experiencd with openstack's common
> command and case.
>
>
> 在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:
>
> -原始邮件-
> *发件人:* Kevin Benton <ke...@benton.pub>
> *发送时间:* 2017年6月13日 星期二
> *收件人:* xiaotie <xiao...@ywe.cc>
> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
> *主题:* Re: Re: [Openstack-operators] IP not been configured in VM os, but
> openstanck assign IP for it
>
>
> That bug just fixes the log noise. That was not the cause of the failure.
>
> Check my suggestion about confirming that DHCP is working.
>
> On Mon, Jun 12, 2017 at 4:11 AM, xiaotie <xiao...@ywe.cc> wrote:
>
>> hi,kevin
>> From this link， I think you have fix this bug. But how can I use it in my
>> environment?
>> Please forgive me, I'm newbie to openstack.
>> In my environment, I use centos7.3, and use yum to install openstack.
>>
>> 在2017-06-12，Kevin Benton <ke...@benton.pub> 写道:
>>
>> -原始邮件-
>> *发件人:* Kevin Benton <ke...@benton.pub>
>> *发送时间:* 2017年6月12日 星期一
>> *收件人:* xiaotie <xiao...@ywe.cc>
>> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
>> *主题:* Re: [Openstack-operators] IP not been configured in VM os, but
>> openstanck assign IP for it
>>
>>
>> I believe that error is actually unrelated (bug reported here for that
>> https://bugs.launchpad.net/neutron/+bug/1697383 ).
>>
>> Do you have the DHCP agent running and is it's port active on the
>> network? You should be able to ping the DHCP address from the 192.168.5
>> network.
>>
>> If you don't have the DHCP agent, you will need to manually assign the IP
>> in your instance.
>>
>> On Sun, Jun 11, 2017 at 11:40 PM, xiaotie <xiao...@ywe.cc> wrote:
>>
>>>
>>> I lanch an instance, but the instance has not IP when I run command
>>>   'ip addr'.But router has assign ip for it.
>>>
>>>   My environment is:
>>>   two vms in virtualbox
>>>   each vm has two ethernet, 192.168.5.0/24 use bridge network; 10.0.0.0/24 
>>> use nat network, both is ok
>>>   I lanch provider network, and router ip is 192.168.5.203, I can ping it 
>>> on the host.
>>>   openstack instance has got an ip,192.168.5.205, I can see it in network 
>>> top0loy of the dashboard, and I can see provider network port is up,but I 
>>> can't ping it.
>>>
>>>   Router info
>>>   
>>> +--++--+-+-+---+
>>>   | id   | name   | tenant_id   
>>>  | external_gateway_info   | distributed | ha|
>>>   
>>> +--++--+-+-+---+
>>>   | efdc40ab-9425-4795-949e-6774eabceed0 | router | 
>>> dfeb844b4942417e9e2d1299c49d1a3a | {"network_id":  
>>> | False   | False |
>>>   |  || 
>>>  | "1807f022-b989-4725-9d25-7d176b28ec72", | |   |
>>>   |  || 
>>>  | "enable_snat": true,| |   |
>>>   |  || 
>>>  | "external_fixed_ips": [{"subnet_id":| |   |
>>>   |  || 
>>>  | "59fc76f2-c666-4693-b0f6-2a96a0189ef7", | |   |
>>>   |  

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[xiaotie]

Thank you kevin.
I just edit neutone code file and log nosise disapper.

As you say, the vm does not automate be configured ip address. But when I 
configure the address that openstack assign to it in the vm os, I can ping 
local network,but I can't
ping 8.8.8.8. On my physical server in the same local network , I can ping 
8.8.8.8

And another tiny question, how can I get dhcp address, and can you give me some 
advice about which doc I can get experiencd with openstack's common command and 
case.


在2017-06-13，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月13日 星期二
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: Re: [Openstack-operators] IP not been configured in VM os, but 
openstanck assign IP for it

That bug just fixes the log noise. That was not the cause of the failure.

Check my suggestion about confirming that DHCP is working.

On Mon, Jun 12, 2017 at 4:11 AM, xiaotie <xiao...@ywe.cc> wrote:
hi,kevin
From this link， I think you have fix this bug. But how can I use it in my 
environment?
Please forgive me, I'm newbie to openstack.
In my environment, I use centos7.3, and use yum to install openstack.

 在2017-06-12，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月12日 星期一
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: [Openstack-operators] IP not been configured in VM os, but openstanck 
assign IP for it

I believe that error is actually unrelated (bug reported here for that 
https://bugs.launchpad.net/neutron/+bug/1697383 ).


Do you have the DHCP agent running and is it's port active on the network? You 
should be able to ping the DHCP address from the 192.168.5 network.


If you don't have the DHCP agent, you will need to manually assign the IP in 
your instance.


On Sun, Jun 11, 2017 at 11:40 PM, xiaotie <xiao...@ywe.cc> wrote:

I lanch an instance, but the instance has not IP when I run command
  'ip addr'.But router has assign ip for it.

  My environment is:
  two vms in virtualbox
  each vm has two ethernet, 192.168.5.0/24 use bridge network; 10.0.0.0/24 use 
nat network, both is ok
  I lanch provider network, and router ip is 192.168.5.203, I can ping it on 
the host.
  openstack instance has got an ip,192.168.5.205, I can see it in network 
top0loy of the dashboard, and I can see provider network port is up,but I can't 
ping it.

  Router info
  
+--++--+-+-+---+
  | id   | name   | tenant_id   
 | external_gateway_info   | distributed | ha|
  
+--++--+-+-+---+
  | efdc40ab-9425-4795-949e-6774eabceed0 | router | 
dfeb844b4942417e9e2d1299c49d1a3a | {"network_id":  | 
False   | False |
  |  || 
 | "1807f022-b989-4725-9d25-7d176b28ec72", | |   |
  |  || 
 | "enable_snat": true,| |   |
  |  || 
 | "external_fixed_ips": [{"subnet_id":| |   |
  |  || 
 | "59fc76f2-c666-4693-b0f6-2a96a0189ef7", | |   |
  |  || 
 | "ip_address": "192.168.5.203"}]}| |   |
  
+--++--+-+-+---+

  Port status
  名称固定IP连接设备状态  管理状态动作
  (85f154ee-1dd6)   192.168.5.205 compute:None  运行中 UP

  when i lanch an instance, I  got the following error on the compute node:
  2017-06-12 06:49:43.610 20776 INFO neutron.agent.securitygroups_rpc 
[req-4fcd8220-8713-469c-9564-1d1eebf30675 472ca430fc46406abac12d2bb877326f 
dfeb844b4942417e9e2d1299c49d1a3a - - -] Security group member updated 
[u'b7da029d-70f0-4ac2-af09-fea4d0e8e516']
  2017-06-12 06:49:45.354 20776 INFO neutron.agent.securitygroups_rpc 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Refresh firewall rules
  2017-06-12 06:49:47.358 20776 INFO neutron.agent.securitygroups_rpc 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Preparing filters for 
devices set(['tap9db05558-8e'])
  2017-06-12 06:49:

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

That bug just fixes the log noise. That was not the cause of the failure.

Check my suggestion about confirming that DHCP is working.

On Mon, Jun 12, 2017 at 4:11 AM, xiaotie <xiao...@ywe.cc> wrote:

> hi,kevin
> From this link， I think you have fix this bug. But how can I use it in my
> environment?
> Please forgive me, I'm newbie to openstack.
> In my environment, I use centos7.3, and use yum to install openstack.
>
> 在2017-06-12，Kevin Benton <ke...@benton.pub> 写道:
>
> -原始邮件-
> *发件人:* Kevin Benton <ke...@benton.pub>
> *发送时间:* 2017年6月12日 星期一
> *收件人:* xiaotie <xiao...@ywe.cc>
> *抄送:* OpenStack Operators <openstack-operators@lists.openstack.org>
> *主题:* Re: [Openstack-operators] IP not been configured in VM os, but
> openstanck assign IP for it
>
>
> I believe that error is actually unrelated (bug reported here for that
> https://bugs.launchpad.net/neutron/+bug/1697383 ).
>
> Do you have the DHCP agent running and is it's port active on the network?
> You should be able to ping the DHCP address from the 192.168.5 network.
>
> If you don't have the DHCP agent, you will need to manually assign the IP
> in your instance.
>
> On Sun, Jun 11, 2017 at 11:40 PM, xiaotie <xiao...@ywe.cc> wrote:
>
>>
>> I lanch an instance, but the instance has not IP when I run command
>>   'ip addr'.But router has assign ip for it.
>>
>>   My environment is:
>>   two vms in virtualbox
>>   each vm has two ethernet, 192.168.5.0/24 use bridge network; 10.0.0.0/24 
>> use nat network, both is ok
>>   I lanch provider network, and router ip is 192.168.5.203, I can ping it on 
>> the host.
>>   openstack instance has got an ip,192.168.5.205, I can see it in network 
>> top0loy of the dashboard, and I can see provider network port is up,but I 
>> can't ping it.
>>
>>   Router info
>>   
>> +--++--+-+-+---+
>>   | id   | name   | tenant_id
>> | external_gateway_info   | distributed | ha|
>>   
>> +--++--+-+-+---+
>>   | efdc40ab-9425-4795-949e-6774eabceed0 | router | 
>> dfeb844b4942417e9e2d1299c49d1a3a | {"network_id":  | 
>> False   | False |
>>   |  ||  
>> | "1807f022-b989-4725-9d25-7d176b28ec72", | |   |
>>   |  ||  
>> | "enable_snat": true,| |   |
>>   |  ||  
>> | "external_fixed_ips": [{"subnet_id":| |   |
>>   |  ||  
>> | "59fc76f2-c666-4693-b0f6-2a96a0189ef7", | |   |
>>   |  ||  
>> | "ip_address": "192.168.5.203"}]}| |   |
>>   
>> +--++--+-+-+---+
>>
>>   Port status
>>   名称 固定IP连接设备状态  管理状态动作
>>   (85f154ee-1dd6)192.168.5.205 compute:None  运行中 UP
>>
>>   when i lanch an instance, I  got the following error on the compute node:
>>   2017-06-12 06:49:43.610 20776 INFO neutron.agent.securitygroups_rpc 
>> [req-4fcd8220-8713-469c-9564-1d1eebf30675 472ca430fc46406abac12d2bb877326f 
>> dfeb844b4942417e9e2d1299c49d1a3a - - -] Security group member updated 
>> [u'b7da029d-70f0-4ac2-af09-fea4d0e8e516']
>>   2017-06-12 06:49:45.354 20776 INFO neutron.agent.securitygroups_rpc 
>> [req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Refresh firewall rules
>>   2017-06-12 06:49:47.358 20776 INFO neutron.agent.securitygroups_rpc 
>> [req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Preparing filters for 
>> devices set(['tap9db05558-8e'])
>>   2017-06-12 06:49:49.273 20776 INFO 
>> neutron.plugins.ml2.drivers.agent._common_agent 
>> [req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Port tap9db05558-8e 
>> updated. Details: {u'profile': {}, u'network_qos_policy_id': None, 
>> u'q

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[xiaotie]

hi,kevin
From this link， I think you have fix this bug. But how can I use it in my 
environment?
Please forgive me, I'm newbie to openstack.
In my environment, I use centos7.3, and use yum to install openstack.

 在2017-06-12，Kevin Benton <ke...@benton.pub> 写道:-原始邮件-
 发件人: Kevin Benton <ke...@benton.pub>
 发送时间: 2017年6月12日 星期一
 收件人: xiaotie <xiao...@ywe.cc>
 抄送: OpenStack Operators <openstack-operators@lists.openstack.org>
 主题: Re: [Openstack-operators] IP not been configured in VM os, but openstanck 
assign IP for it

I believe that error is actually unrelated (bug reported here for that 
https://bugs.launchpad.net/neutron/+bug/1697383 ).


Do you have the DHCP agent running and is it's port active on the network? You 
should be able to ping the DHCP address from the 192.168.5 network.


If you don't have the DHCP agent, you will need to manually assign the IP in 
your instance.


On Sun, Jun 11, 2017 at 11:40 PM, xiaotie <xiao...@ywe.cc> wrote:

I lanch an instance, but the instance has not IP when I run command
  'ip addr'.But router has assign ip for it.

  My environment is:
  two vms in virtualbox
  each vm has two ethernet, 192.168.5.0/24 use bridge network; 10.0.0.0/24 use 
nat network, both is ok
  I lanch provider network, and router ip is 192.168.5.203, I can ping it on 
the host.
  openstack instance has got an ip,192.168.5.205, I can see it in network 
top0loy of the dashboard, and I can see provider network port is up,but I can't 
ping it.

  Router info
  
+--++--+-+-+---+
  | id   | name   | tenant_id   
 | external_gateway_info   | distributed | ha|
  
+--++--+-+-+---+
  | efdc40ab-9425-4795-949e-6774eabceed0 | router | 
dfeb844b4942417e9e2d1299c49d1a3a | {"network_id":  | 
False   | False |
  |  || 
 | "1807f022-b989-4725-9d25-7d176b28ec72", | |   |
  |  || 
 | "enable_snat": true,| |   |
  |  || 
 | "external_fixed_ips": [{"subnet_id":| |   |
  |  || 
 | "59fc76f2-c666-4693-b0f6-2a96a0189ef7", | |   |
  |  || 
 | "ip_address": "192.168.5.203"}]}| |   |
  
+--++--+-+-+---+

  Port status
  名称固定IP连接设备状态  管理状态动作
  (85f154ee-1dd6)   192.168.5.205 compute:None  运行中 UP

  when i lanch an instance, I  got the following error on the compute node:
  2017-06-12 06:49:43.610 20776 INFO neutron.agent.securitygroups_rpc 
[req-4fcd8220-8713-469c-9564-1d1eebf30675 472ca430fc46406abac12d2bb877326f 
dfeb844b4942417e9e2d1299c49d1a3a - - -] Security group member updated 
[u'b7da029d-70f0-4ac2-af09-fea4d0e8e516']
  2017-06-12 06:49:45.354 20776 INFO neutron.agent.securitygroups_rpc 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Refresh firewall rules
  2017-06-12 06:49:47.358 20776 INFO neutron.agent.securitygroups_rpc 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Preparing filters for 
devices set(['tap9db05558-8e'])
  2017-06-12 06:49:49.273 20776 INFO 
neutron.plugins.ml2.drivers.agent._common_agent 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Port tap9db05558-8e 
updated. Details: {u'profile': {}, u'network_qos_policy_id': None, 
u'qos_policy_id': None, u'allowed_address_pairs': [], u'admin_state_up': True, 
u'network_id': u'1807f022-b989-4725-9d25-7d176b28ec72', u'segmentation_id': 
None, u'device_owner': u'compute:nova', u'physical_network': u'provider', 
u'mac_address': u'fa:16:3e:61:90:f5', u'device': u'tap9db05558-8e', 
u'port_security_enabled': True, u'port_id': 
u'9db05558-8e87-4a24-928c-cd97b777', u'fixed_ips': [{u'subnet_id': 
u'59fc76f2-c666-4693-b0f6-2a96a0189ef7', u'ip_address': u'192.168.5.211'}], 
u'network_type': u'flat'}
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Error during notification 
for 
neutron.services.trunk.drivers.linuxbridge.agent.driver.LinuxBridgeTrunkDriver.agent_port_change--9223372036853960796
 port_device, after_update
  2017-06-12 06:49:50.591 2

Re: [Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[Kevin Benton]

I believe that error is actually unrelated (bug reported here for that
https://bugs.launchpad.net/neutron/+bug/1697383 ).

Do you have the DHCP agent running and is it's port active on the network?
You should be able to ping the DHCP address from the 192.168.5 network.

If you don't have the DHCP agent, you will need to manually assign the IP
in your instance.

On Sun, Jun 11, 2017 at 11:40 PM, xiaotie  wrote:

>
> I lanch an instance, but the instance has not IP when I run command
>   'ip addr'.But router has assign ip for it.
>
>   My environment is:
>   two vms in virtualbox
>   each vm has two ethernet, 192.168.5.0/24 use bridge network; 10.0.0.0/24 
> use nat network, both is ok
>   I lanch provider network, and router ip is 192.168.5.203, I can ping it on 
> the host.
>   openstack instance has got an ip,192.168.5.205, I can see it in network 
> top0loy of the dashboard, and I can see provider network port is up,but I 
> can't ping it.
>
>   Router info
>   
> +--++--+-+-+---+
>   | id   | name   | tenant_id 
>| external_gateway_info   | distributed | ha|
>   
> +--++--+-+-+---+
>   | efdc40ab-9425-4795-949e-6774eabceed0 | router | 
> dfeb844b4942417e9e2d1299c49d1a3a | {"network_id":  | 
> False   | False |
>   |  ||   
>| "1807f022-b989-4725-9d25-7d176b28ec72", | |   |
>   |  ||   
>| "enable_snat": true,| |   |
>   |  ||   
>| "external_fixed_ips": [{"subnet_id":| |   |
>   |  ||   
>| "59fc76f2-c666-4693-b0f6-2a96a0189ef7", | |   |
>   |  ||   
>| "ip_address": "192.168.5.203"}]}| |   |
>   
> +--++--+-+-+---+
>
>   Port status
>   名称  固定IP连接设备状态  管理状态动作
>   (85f154ee-1dd6) 192.168.5.205 compute:None  运行中 UP
>
>   when i lanch an instance, I  got the following error on the compute node:
>   2017-06-12 06:49:43.610 20776 INFO neutron.agent.securitygroups_rpc 
> [req-4fcd8220-8713-469c-9564-1d1eebf30675 472ca430fc46406abac12d2bb877326f 
> dfeb844b4942417e9e2d1299c49d1a3a - - -] Security group member updated 
> [u'b7da029d-70f0-4ac2-af09-fea4d0e8e516']
>   2017-06-12 06:49:45.354 20776 INFO neutron.agent.securitygroups_rpc 
> [req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Refresh firewall rules
>   2017-06-12 06:49:47.358 20776 INFO neutron.agent.securitygroups_rpc 
> [req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Preparing filters for 
> devices set(['tap9db05558-8e'])
>   2017-06-12 06:49:49.273 20776 INFO 
> neutron.plugins.ml2.drivers.agent._common_agent 
> [req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Port tap9db05558-8e 
> updated. Details: {u'profile': {}, u'network_qos_policy_id': None, 
> u'qos_policy_id': None, u'allowed_address_pairs': [], u'admin_state_up': 
> True, u'network_id': u'1807f022-b989-4725-9d25-7d176b28ec72', 
> u'segmentation_id': None, u'device_owner': u'compute:nova', 
> u'physical_network': u'provider', u'mac_address': u'fa:16:3e:61:90:f5', 
> u'device': u'tap9db05558-8e', u'port_security_enabled': True, u'port_id': 
> u'9db05558-8e87-4a24-928c-cd97b777', u'fixed_ips': [{u'subnet_id': 
> u'59fc76f2-c666-4693-b0f6-2a96a0189ef7', u'ip_address': u'192.168.5.211'}], 
> u'network_type': u'flat'}
>   2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager 
> [req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Error during 
> notification for 
> neutron.services.trunk.drivers.linuxbridge.agent.driver.LinuxBridgeTrunkDriver.agent_port_change--9223372036853960796
>  port_device, after_update
>   2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager Traceback 
> (most recent call last):
>   2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager   File 
> "/usr/lib/python2.7/site-packages/neutron/callbacks/manager.py", line 146, in 
> _notify_loop
>   2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager 
> callback(resource, event, trigger, **kwargs)
>   2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager   File 
> 

[Openstack-operators] IP not been configured in VM os, but openstanck assign IP for it

[xiaotie]

I lanch an instance, but the instance has not IP when I run command
  'ip addr'.But router has assign ip for it.

  My environment is:
  two vms in virtualbox
  each vm has two ethernet, 192.168.5.0/24 use bridge network; 10.0.0.0/24 use 
nat network, both is ok
  I lanch provider network, and router ip is 192.168.5.203, I can ping it on 
the host.
  openstack instance has got an ip,192.168.5.205, I can see it in network 
top0loy of the dashboard, and I can see provider network port is up,but I can't 
ping it.

  Router info
  
+--++--+-+-+---+
  | id   | name   | tenant_id   
 | external_gateway_info   | distributed | ha|
  
+--++--+-+-+---+
  | efdc40ab-9425-4795-949e-6774eabceed0 | router | 
dfeb844b4942417e9e2d1299c49d1a3a | {"network_id":  | 
False   | False |
  |  || 
 | "1807f022-b989-4725-9d25-7d176b28ec72", | |   |
  |  || 
 | "enable_snat": true,| |   |
  |  || 
 | "external_fixed_ips": [{"subnet_id":| |   |
  |  || 
 | "59fc76f2-c666-4693-b0f6-2a96a0189ef7", | |   |
  |  || 
 | "ip_address": "192.168.5.203"}]}| |   |
  
+--++--+-+-+---+

  Port status
  名称固定IP连接设备状态  管理状态动作
  (85f154ee-1dd6)   192.168.5.205 compute:None  运行中 UP

  when i lanch an instance, I  got the following error on the compute node:
  2017-06-12 06:49:43.610 20776 INFO neutron.agent.securitygroups_rpc 
[req-4fcd8220-8713-469c-9564-1d1eebf30675 472ca430fc46406abac12d2bb877326f 
dfeb844b4942417e9e2d1299c49d1a3a - - -] Security group member updated 
[u'b7da029d-70f0-4ac2-af09-fea4d0e8e516']
  2017-06-12 06:49:45.354 20776 INFO neutron.agent.securitygroups_rpc 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Refresh firewall rules
  2017-06-12 06:49:47.358 20776 INFO neutron.agent.securitygroups_rpc 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Preparing filters for 
devices set(['tap9db05558-8e'])
  2017-06-12 06:49:49.273 20776 INFO 
neutron.plugins.ml2.drivers.agent._common_agent 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Port tap9db05558-8e 
updated. Details: {u'profile': {}, u'network_qos_policy_id': None, 
u'qos_policy_id': None, u'allowed_address_pairs': [], u'admin_state_up': True, 
u'network_id': u'1807f022-b989-4725-9d25-7d176b28ec72', u'segmentation_id': 
None, u'device_owner': u'compute:nova', u'physical_network': u'provider', 
u'mac_address': u'fa:16:3e:61:90:f5', u'device': u'tap9db05558-8e', 
u'port_security_enabled': True, u'port_id': 
u'9db05558-8e87-4a24-928c-cd97b777', u'fixed_ips': [{u'subnet_id': 
u'59fc76f2-c666-4693-b0f6-2a96a0189ef7', u'ip_address': u'192.168.5.211'}], 
u'network_type': u'flat'}
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager 
[req-bfc74178-179f-4abd-bdb2-25d66ce36107 - - - - -] Error during notification 
for 
neutron.services.trunk.drivers.linuxbridge.agent.driver.LinuxBridgeTrunkDriver.agent_port_change--9223372036853960796
 port_device, after_update
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager Traceback (most 
recent call last):
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/callbacks/manager.py", line 146, in 
_notify_loop
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager 
callback(resource, event, trigger, **kwargs)
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/services/trunk/drivers/linuxbridge/agent/driver.py",
 line 94, in agent_port_change
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager trunk = 
self._tapi.get_trunk(context, device_details['port_id'])
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/services/trunk/drivers/linuxbridge/agent/driver.py",
 line 196, in get_trunk
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager 
self.put_trunk(port_id, self._fetch_trunk(context, port_id))
  2017-06-12 06:49:50.591 20776 ERROR neutron.callbacks.manager   File