-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
xcvrd crash on Celestica dx010 and S6100 #6978
Labels
Comments
yxieca
changed the title
xcvrd crash on Celestica dx010
xcvrd crash on Celestica dx010 and S6100
Mar 7, 2021
is this a regression? @jleveque |
reopen this issue for tracking the root cause. I am concerned about these continuous regressions. |
Yes. Regression was introduced by sonic-net/sonic-platform-daemons#72. I have opened a fix here: sonic-net/sonic-platform-daemons#162. |
jleveque
added a commit
to sonic-net/sonic-platform-daemons
that referenced
this issue
Mar 9, 2021
…'N/A' (#162) Currently, some vendors are using custom transceiver info parsers which do not yet provide the `dom_capability` field in the results of `get_transceiver_info()`. However, PR #72 introduced storing this value to State DB under the assumption that it would always be present. On platforms where this value is not present, it would cause xcvrd to crash (see issue: sonic-net/sonic-buildimage#6978). This change will prevent a crash if it is not present, and will in turn save `'N/A'` as the `dom_capability` value in State DB.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Nightly test is failing on Celestica DX010 platform consistently because xcvrd is crashing
From show version output. It appears that the platform API implementation is either missing or wrong.
Also found this issue on S6100. The problem happened between image 459 and 467. The most likely regression is from PR #6957
Steps to reproduce the issue:
Describe the results you received:
/var/log/syslog:Mar 7 00:10:42.585233 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd Traceback (most recent call last):
/var/log/syslog:Mar 7 00:10:42.585514 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd File "/usr/local/bin/xcvrd", line 8, in
/var/log/syslog:Mar 7 00:10:42.585710 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd sys.exit(main())
/var/log/syslog:Mar 7 00:10:42.585872 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd File "/usr/local/lib/python2.7/dist-packages/xcvrd/xcvrd.py", line 1379, in main
/var/log/syslog:Mar 7 00:10:42.586022 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd xcvrd.run()
/var/log/syslog:Mar 7 00:10:42.586169 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd File "/usr/local/lib/python2.7/dist-packages/xcvrd/xcvrd.py", line 1327, in run
/var/log/syslog:Mar 7 00:10:42.586332 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd self.init()
/var/log/syslog:Mar 7 00:10:42.586493 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd File "/usr/local/lib/python2.7/dist-packages/xcvrd/xcvrd.py", line 1292, in init
/var/log/syslog:Mar 7 00:10:42.586657 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd post_port_sfp_dom_info_to_db(is_warm_start, self.stop_event)
/var/log/syslog:Mar 7 00:10:42.586836 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd File "/usr/local/lib/python2.7/dist-packages/xcvrd/xcvrd.py", line 486, in post_port_sfp_dom_info_to_db
/var/log/syslog:Mar 7 00:10:42.587001 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd post_port_sfp_info_to_db(logical_port_name, int_tbl[asic_index], transceiver_dict, stop_event)
/var/log/syslog:Mar 7 00:10:42.587158 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd File "/usr/local/lib/python2.7/dist-packages/xcvrd/xcvrd.py", line 302, in post_port_sfp_info_to_db
/var/log/syslog:Mar 7 00:10:42.587315 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd ('dom_capability',port_info_dict['dom_capability']),
/var/log/syslog:Mar 7 00:10:42.587472 str-dx010-acs-4 INFO pmon#/supervisord: xcvrd KeyError: 'dom_capability'
Describe the results you expected:
system being healthy.
Output of
show version
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: