Public bug reported:
Bug performance
1）compute node without L3 agent and DHCP agent，But in the control node can see
the compute node’s L3 agent and DHCP agent work normally
[root@controller ~(keystone_admin)]# neutron agent-list|grep Slot12
| 2e15ea73-7abf-445c-a033-2bb94983c09a | PCI NIC Switch agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-pci-sriov-nic-agent |
| 3ec4e476-bf1c-4a1c-baf7-2b6429389410 | Metadata agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-metadata-agent |
| b769ecdf-4319-430e-b3af-bfb4e2d20f53 | L3 agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-l3-agent |
| d2254fa9-db33-4277-9853-3dfe7ef9c643 | Open vSwitch agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-openvswitch-agent |
| d639783e-0ff3-4777-9ce2-2c85512637f0 | DHCP agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-dhcp-agent |
[root@SBCRRack3Shelf1Slot11 ~(keystone_admin)]#
[root@compute ~(keystone_admin)]# neutron agent-show
b769ecdf-4319-430e-b3af-bfb4e2d20f53
+---------------------+-------------------------------------------------------------------------------+
| Field | Value
|
+---------------------+-------------------------------------------------------------------------------+
| admin_state_up | True
|
| agent_type | L3 agent
|
| alive | True
|
| binary | neutron-l3-agent
|
| configurations | {
|
| | "router_id": "",
|
| | "agent_mode": "legacy",
|
| | "gateway_external_network_id": "",
|
| | "handle_internal_only_routers": true,
|
| | "use_namespaces": true,
|
| | "routers": 0,
|
| | "interfaces": 0,
|
| | "floating_ips": 0,
|
| | "interface_driver":
"neutron.agent.linux.interface.OVSInterfaceDriver", |
| | "external_network_bridge": "br-ex",
|
| | "ex_gw_ports": 0
|
| | }
|
| created_at | 2016-04-08 05:55:31
|
| description |
|
| heartbeat_timestamp | 2016-04-14 02:29:38
|
| host | SBCRRack3Shelf1Slot12
|
| id | b769ecdf-4319-430e-b3af-bfb4e2d20f53
|
| started_at | 2016-04-13 09:42:49
|
| topic | l3_agent
|
+---------------------+-------------------------------------------------------------------------------+
[root@SBCRRack3Shelf1Slot11 ~(keystone_admin)]#
Bug reason
2）After check，the agent is down,so heartbeat_timestamp is not updated.
However,for some reason,the controller node's current time changed(Earlier
than heartbeat_timestamp) ,The controller node 's current time minus the agent'
s heartbeat_timestamp negative,So the controlerr node executing “ neutron
agent-list” command, we can see the aegnt status is :-)
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1579631
Title:
Node time changed，resulting in abnormal state of neutron agent.
Status in neutron:
New
Bug description:
Bug performance
1）compute node without L3 agent and DHCP agent，But in the control node can
see the compute node’s L3 agent and DHCP agent work normally
[root@controller ~(keystone_admin)]# neutron agent-list|grep Slot12
| 2e15ea73-7abf-445c-a033-2bb94983c09a | PCI NIC Switch agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-pci-sriov-nic-agent |
| 3ec4e476-bf1c-4a1c-baf7-2b6429389410 | Metadata agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-metadata-agent |
| b769ecdf-4319-430e-b3af-bfb4e2d20f53 | L3 agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-l3-agent |
| d2254fa9-db33-4277-9853-3dfe7ef9c643 | Open vSwitch agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-openvswitch-agent |
| d639783e-0ff3-4777-9ce2-2c85512637f0 | DHCP agent |
SBCRRack3Shelf1Slot12 | :-) | True | neutron-dhcp-agent |
[root@SBCRRack3Shelf1Slot11 ~(keystone_admin)]#
[root@compute ~(keystone_admin)]# neutron agent-show
b769ecdf-4319-430e-b3af-bfb4e2d20f53
+---------------------+-------------------------------------------------------------------------------+
| Field | Value
|
+---------------------+-------------------------------------------------------------------------------+
| admin_state_up | True
|
| agent_type | L3 agent
|
| alive | True
|
| binary | neutron-l3-agent
|
| configurations | {
|
| | "router_id": "",
|
| | "agent_mode": "legacy",
|
| | "gateway_external_network_id": "",
|
| | "handle_internal_only_routers": true,
|
| | "use_namespaces": true,
|
| | "routers": 0,
|
| | "interfaces": 0,
|
| | "floating_ips": 0,
|
| | "interface_driver":
"neutron.agent.linux.interface.OVSInterfaceDriver", |
| | "external_network_bridge": "br-ex",
|
| | "ex_gw_ports": 0
|
| | }
|
| created_at | 2016-04-08 05:55:31
|
| description |
|
| heartbeat_timestamp | 2016-04-14 02:29:38
|
| host | SBCRRack3Shelf1Slot12
|
| id | b769ecdf-4319-430e-b3af-bfb4e2d20f53
|
| started_at | 2016-04-13 09:42:49
|
| topic | l3_agent
|
+---------------------+-------------------------------------------------------------------------------+
[root@SBCRRack3Shelf1Slot11 ~(keystone_admin)]#
Bug reason
2）After check，the agent is down,so heartbeat_timestamp is not updated.
However,for some reason,the controller node's current time changed(Earlier
than heartbeat_timestamp) ,The controller node 's current time minus the agent'
s heartbeat_timestamp negative,So the controlerr node executing “ neutron
agent-list” command, we can see the aegnt status is :-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1579631/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
