| 2023-07-21 07:12:54 |
Mohankumar |
bug |
|
|
added bug |
| 2023-07-21 07:24:05 |
Mohankumar |
description |
❯ openstack network agent list --router r1 --long
+--------------------------------------+------------+--------------------------------+-------------------+-------+-------+----------------------+----------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+--------------------------------------+------------+--------------------------------+-------------------+-------+-------+----------------------+----------+
| 64865237-5361-4433-b709-02c153bf5d61 | L3 agent | snat1145764.gra5.cloud.ovh.net | nova | :-) | UP | neutron-ovh-l3-agent | unknown |
| fdc16120-5162-4df5-83e7-ab76f9d6cb21 | L3 agent | snat1412427.gra5.cloud.ovh.net | nova | :-) | UP | neutron-ovh-l3-agent | standby |
+--------------------------------------+------------+--------------------------------+-------------------+-------+-------+----------------------+----------+ |
❯ openstack network agent list --router r1 --long
+--------------------------------------+------------+--------------------------------+-------------------+-------+-------+----------------------+----------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+--------------------------------------+------------+--------------------------------+-------------------+-------+-------+----------------------+----------+
| 64865237-5361-4433-b709-02c153bf5d61 | L3 agent | snat1145764.gra5.cloud.ovh.net | nova | :-) | UP | neutron-ovh-l3-agent | unknown |
| fdc16120-5162-4df5-83e7-ab76f9d6cb21 | L3 agent | snat1412427.gra5.cloud.ovh.net | nova | :-) | UP | neutron-ovh-l3-agent | standby |
+--------------------------------------+------------+--------------------------------+-------------------+-------+-------+----------------------+----------+
When neutron-server notices the l3_agent not active /agent health-check not successful. It set l3_agent as "unknown" But when l3_agent active agent like
process force-stop/crash scenarios . When the agent is recovered the l3_agent state not reverted back to original state .
When some update happens on the router , it able to restore the actual state but not after agent is restored / recovered |
|
| 2023-07-21 07:25:05 |
Mohankumar |
neutron: assignee |
|
Mohankumar (mohankumar-n) |
|
| 2023-07-28 14:22:14 |
Bence Romsics |
neutron: status |
New |
Incomplete |
|
| 2023-09-21 05:59:27 |
Mohankumar |
description |
❯ openstack network agent list --router r1 --long
+--------------------------------------+------------+--------------------------------+-------------------+-------+-------+----------------------+----------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+--------------------------------------+------------+--------------------------------+-------------------+-------+-------+----------------------+----------+
| 64865237-5361-4433-b709-02c153bf5d61 | L3 agent | snat1145764.gra5.cloud.ovh.net | nova | :-) | UP | neutron-ovh-l3-agent | unknown |
| fdc16120-5162-4df5-83e7-ab76f9d6cb21 | L3 agent | snat1412427.gra5.cloud.ovh.net | nova | :-) | UP | neutron-ovh-l3-agent | standby |
+--------------------------------------+------------+--------------------------------+-------------------+-------+-------+----------------------+----------+
When neutron-server notices the l3_agent not active /agent health-check not successful. It set l3_agent as "unknown" But when l3_agent active agent like
process force-stop/crash scenarios . When the agent is recovered the l3_agent state not reverted back to original state .
When some update happens on the router , it able to restore the actual state but not after agent is restored / recovered |
❯ openstack network agent list --router r1 --long
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
| 6faf003f-ef57-46a7-a3d4-eb63a8561e09 | L3 agent | req-multi-devstack-stein-85-4568-minion2-mn | nova | XXX | UP | neutron-ovh-l3-agent | unknown |
| bf90fed6-a31d-46a8-8fe9-a9ce587f241d | L3 agent | req-multi-devstack-stein-85-4568-minion1-mn | nova | XXX | UP | neutron-ovh-l3-agent | standby |
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
When neutron-server notices the l3_agent not active /agent health-check not successful. It set l3_agent as "unknown" But when l3_agent active agent like
process force-stop/crash scenarios . When the agent is recovered the l3_agent state not reverted back to original state .
When some update happens on the router , it able to restore the actual state but not after agent is restored / recovered |
|
| 2023-09-21 06:01:19 |
Mohankumar |
description |
❯ openstack network agent list --router r1 --long
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
| 6faf003f-ef57-46a7-a3d4-eb63a8561e09 | L3 agent | req-multi-devstack-stein-85-4568-minion2-mn | nova | XXX | UP | neutron-ovh-l3-agent | unknown |
| bf90fed6-a31d-46a8-8fe9-a9ce587f241d | L3 agent | req-multi-devstack-stein-85-4568-minion1-mn | nova | XXX | UP | neutron-ovh-l3-agent | standby |
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
When neutron-server notices the l3_agent not active /agent health-check not successful. It set l3_agent as "unknown" But when l3_agent active agent like
process force-stop/crash scenarios . When the agent is recovered the l3_agent state not reverted back to original state .
When some update happens on the router , it able to restore the actual state but not after agent is restored / recovered |
❯ openstack network agent list --router r1 --long
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
| 6faf003f-ef57-46a7-a3d4-eb63a8561e09 | L3 agent | req-multi-devstack-stein-85-4568-minion2-mn | nova | XXX | UP | neutron-ovh-l3-agent | unknown |
| bf90fed6-a31d-46a8-8fe9-a9ce587f241d | L3 agent | req-multi-devstack-stein-85-4568-minion1-mn | nova | XXX | UP | neutron-ovh-l3-agent | standby |
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
❯ openstack network agent list --router r1 --long
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
| 6faf003f-ef57-46a7-a3d4-eb63a8561e09 | L3 agent | req-multi-devstack-stein-85-4568-minion2-mn | nova | :-) | UP | neutron-ovh-l3-agent | unknown |
| bf90fed6-a31d-46a8-8fe9-a9ce587f241d | L3 agent | req-multi-devstack-stein-85-4568-minion1-mn | nova | :-) | UP | neutron-ovh-l3-agent | standby |
+--------------------------------------+------------+---------------------------------------------+-------------------+-------+-------+----------------------+----------+
When neutron-server notices the l3_agent not active /agent health-check not successful. It set l3_agent as "unknown" But when l3_agent active agent like
process force-stop/crash scenarios . When the agent is recovered the l3_agent state not reverted back to original state .
When some update happens on the router , it able to restore the actual state but not after agent is restored / recovered |
|
| 2023-09-21 06:01:48 |
Mohankumar |
neutron: status |
Incomplete |
New |
|
| 2023-09-21 06:02:05 |
Mohankumar |
neutron: status |
New |
Incomplete |
|
