-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reset active application code as 'N/A' when port shutdown #550
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: chiourung_huang <[email protected]>
@chiourung please share the output of |
@chiourung please fix the build error |
Update in Description |
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mihirpat1 can you review?
sonic-xcvrd/xcvrd/xcvrd.py
Outdated
@@ -1468,6 +1489,7 @@ def task_worker(self): | |||
self.log_notice("{} Forcing Tx laser OFF".format(lport)) | |||
# Force DataPath re-init | |||
api.tx_disable_channel(media_lanes_mask, True) | |||
self.reset_port_active_apsel_to_db(lport, host_lanes_mask) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chiourung Can we reuse post_port_active_apsel_to_db
function and introduce an additional argument to ignore reading the active application to reduce code replication?
@chiourung Please help in fixing the build failure. |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
The build failure is
|
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
Motivation and Context
In the add_rack test, it would compare the TRANSCEIVER_INFO for two cases:
case 1. config reload (the admin status of Ethernet64 is down in config_db.json)
case 2. config reload (the admin status of Ethernet64 is up in config_db.json) and then shutdown Ethernet64
In case 1. it would not do CMIS init and the active application is 'N/A'.
In case 2. it would do CMIS init first and then disable TX. The active application would retain the value of the last CMIS init.
=> Modify the code to reset the active application on port shutdown to ensure that the active application would be the same for the above two cases.
How Has This Been Tested?
Additional Information (Optional)