Skip to content

Port nni removed#514

Draft
YufengXin wants to merge 4 commits intomainfrom
478-link-status-not-updating-to-error-after-nni-attribute-removal-use-case-9
Draft

Port nni removed#514
YufengXin wants to merge 4 commits intomainfrom
478-link-status-not-updating-to-error-after-nni-attribute-removal-use-case-9

Conversation

@YufengXin
Copy link
Collaborator

No description provided.

@YufengXin YufengXin self-assigned this Feb 3, 2026
@YufengXin YufengXin marked this pull request as draft February 3, 2026 22:26
@coveralls
Copy link

coveralls commented Feb 3, 2026

Pull Request Test Coverage Report for Build 22245020051

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 53.876%

Totals Coverage Status
Change from base Build 22150611686: 0.0%
Covered Lines: 1265
Relevant Lines: 2348

💛 - Coveralls

Yufeng Xin added 3 commits February 11, 2026 14:04
…pdating-to-error-after-nni-attribute-removal-use-case-9
…pdating-to-error-after-nni-attribute-removal-use-case-9
@YufengXin
Copy link
Collaborator Author

YufengXin commented Feb 25, 2026

sdx-controller-1 | 2026-02-25T19:51:39.821652706Z DEBUG:sdx_controller.handlers.connection_handler:Found the down port record for port urn:sdx:port:ampath.net:Ampath1:50! sdx-controller-1 | 2026-02-25T19:51:39.822305251Z INFO:sdx_controller.handlers.connection_handler:Updating connection 6b6ba034-975b-45f1-9c5d-b4acf96bc3d5 status to 'down'. sdx-controller-1 | 2026-02-25T19:51:39.823253842Z DEBUG:sdx_controller.handlers.connection_handler:Connection status updated for 6b6ba034-975b-45f1-9c5d-b4acf96bc3d5 sdx-controller-1 | 2026-02-25T19:51:39.823260204Z INFO:sdx_controller.handlers.lc_message_handler:Adding topology ampath.net to db. sdx-controller-1 | 2026-02-25T19:51:39.825682001Z INFO:sdx_controller.handlers.lc_message_handler:Save to database complete. sdx-controller-1 | 2026-02-25T19:51:39.825762522Z DEBUG:sdx_controller.messaging.rpc_queue_consumer:MQ received message:b'{"lc_domain": "ampath.net", "msg_type": "oxp_conn_response", "service_id": "6b6ba034-975b-45f1-9c5d-b4acf96bc3d5", "operation": "delete", "oxp_response_code": 201, "oxp_response": "L2VPN Deleted"}' sdx-controller-1 | 2026-02-25T19:51:39.825769756Z INFO:sdx_controller.handlers.lc_message_handler:MQ received message:b'{"lc_domain": "ampath.net", "msg_type": "oxp_conn_response", "service_id": "6b6ba034-975b-45f1-9c5d-b4acf96bc3d5", "operation": "delete", "oxp_response_code": 201, "oxp_response": "L2VPN Deleted"}' sdx-controller-1 | 2026-02-25T19:51:39.825863632Z INFO:sdx_controller.handlers.lc_message_handler:Received OXP connection response. sdx-controller-1 | 2026-02-25T19:51:39.827290161Z INFO:sdx_controller.handlers.lc_message_handler:Connection updated: 6b6ba034-975b-45f1-9c5d-b4acf96bc3d5 sdx-controller-1 | 2026-02-25T19:51:39.827298106Z DEBUG:sdx_controller.messaging.rpc_queue_consumer:MQ received message:b'{"lc_domain": "sax.net", "msg_type": "oxp_conn_response", "service_id": "6b6ba034-975b-45f1-9c5d-b4acf96bc3d5", "operation": "delete", "oxp_response_code": 201, "oxp_response": "L2VPN Deleted"}' sdx-controller-1 | 2026-02-25T19:51:39.827369750Z INFO:sdx_controller.handlers.lc_message_handler:MQ received message:b'{"lc_domain": "sax.net", "msg_type": "oxp_conn_response", "service_id": "6b6ba034-975b-45f1-9c5d-b4acf96bc3d5", "operation": "delete", "oxp_response_code": 201, "oxp_response": "L2VPN Deleted"}' sdx-controller-1 | 2026-02-25T19:51:39.827375120Z INFO:sdx_controller.handlers.lc_message_handler:Received OXP connection response. sdx-controller-1 | 2026-02-25T19:51:39.828775099Z INFO:sdx_controller.handlers.lc_message_handler:Connection updated: 6b6ba034-975b-45f1-9c5d-b4acf96bc3d5 sdx-controller-1 | 2026-02-25T19:51:55.056439769Z DEBUG:sdx_controller.messaging.rpc_queue_consumer:MQ received message:b'{"lc_domain": "sax.net", "msg_type": "oxp_conn_response", "service_id": "6b6ba034-975b-45f1-9c5d-b4acf96bc3d5", "operation": "post", "oxp_response_code": 201, "oxp_response": {"service_id": "4b334e727e5649"}}' sdx-controller-1 | 2026-02-25T19:51:55.056459196Z INFO:sdx_controller.handlers.lc_message_handler:MQ received message:b'{"lc_domain": "sax.net", "msg_type": "oxp_conn_response", "service_id": "6b6ba034-975b-45f1-9c5d-b4acf96bc3d5", "operation": "post", "oxp_response_code": 201, "oxp_response": {"service_id": "4b334e727e5649"}}' sdx-controller-1 | 2026-02-25T19:51:55.056490735Z INFO:sdx_controller.handlers.lc_message_handler:Received OXP connection response. sdx-controller-1 | 2026-02-25T19:51:55.058690395Z INFO:sdx_controller.handlers.lc_message_handler:Connection updated: 6b6ba034-975b-45f1-9c5d-b4acf96bc3d5 sdx-controller-1 | 2026-02-25T19:51:57.275081963Z DEBUG:sdx_controller.messaging.rpc_queue_consumer:MQ received message:b'{"lc_domain": "ampath.net", "msg_type": "oxp_conn_response", "service_id": "6b6ba034-975b-45f1-9c5d-b4acf96bc3d5", "operation": "post", "oxp_response_code": 201, "oxp_response": {"service_id": "421aebf496444f"}}' sdx-controller-1 | 2026-02-25T19:51:57.275126095Z INFO:sdx_controller.handlers.lc_message_handler:MQ received message:b'{"lc_domain": "ampath.net", "msg_type": "oxp_conn_response", "service_id": "6b6ba034-975b-45f1-9c5d-b4acf96bc3d5", "operation": "post", "oxp_response_code": 201, "oxp_response": {"service_id": "421aebf496444f"}}' sdx-controller-1 | 2026-02-25T19:51:57.275140673Z INFO:sdx_controller.handlers.lc_message_handler:Received OXP connection response. sdx-controller-1 | 2026-02-25T19:51:57.278322828Z ERROR:sdx_controller.messaging.rpc_queue_consumer:Failed to process LC message: Invalid transition from DOWN to UP -- Traceback (most recent call last):, File "/opt/venv/lib/python3.11/site-packages/sdx_controller/messaging/rpc_queue_consumer.py", line 371, in start_sdx_consumer, lc_message_handler.process_lc_json_msg(, File "/opt/venv/lib/python3.11/site-packages/sdx_controller/handlers/lc_message_handler.py", line 77, in process_lc_json_msg, connection, _ = connection_state_machine(, ^^^^^^^^^^^^^^^^^^^^^^^^^, File "/opt/venv/lib/python3.11/site-packages/sdx_controller/handlers/connection_handler.py", line 854, in connection_state_machine, conn_sm.transition(new_state), File "/opt/venv/lib/python3.11/site-packages/sdx_datamodel/connection_sm.py", line 249, in transition, raise ConnectionSMException(, sdx_datamodel.connection_sm.ConnectionSMException: Invalid transition from DOWN to UP,

------------Observed in test_21_use_case_topology.py::TestE2ETopologyUseCases::test_091_port_missing_nni------

  1. all ports "down" from OXPs tenet and sax updates
  2. above loved msg: OXP breakdown response: first "delete", then "operation"....

@YufengXin
Copy link
Collaborator Author

@gretelliz @italovalcy see above logs. Were there some recent updates in Kytos?

  1. All the ports from tenet and sax update were "down"
  2. After the controller told the oxps to delete, the OXPs reported breakdowns "delete", then "operation".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Link status not updating to "error" after nni attribute removal (Use Case 9)

2 participants