You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platform API is not recognizing reboot-cause after powercycle of 9332.
show reboot-cause
Unknown
root@str2-z9332f-01:~# show reboot-cause history
Name Cause Time User Comment
------------------- ----------- ------------------------------- ------ ---------
2021_08_26_14_08_39 Unknown N/A N/A N/A
2021_08_26_13_58_46 reboot Thu 26 Aug 2021 01:57:33 PM UTC admin N/A
2021_08_26_13_52_18 reboot Thu 26 Aug 2021 01:51:01 PM UTC admin N/A
2021_08_26_13_46_27 reboot Thu 26 Aug 2021 01:45:12 PM UTC admin N/A
2021_08_26_13_36_41 Unknown N/A N/A N/A
2021_08_26_13_29_37 warm-reboot Thu 26 Aug 2021 01:28:35 PM UTC admin N/A
2021_08_26_13_23_24 fast-reboot Thu 26 Aug 2021 01:22:32 PM UTC admin N/A
2021_08_26_13_17_23 soft-reboot Thu 26 Aug 2021 01:17:00 PM UTC admin N/A
2021_08_26_13_12_04 reboot Thu 26 Aug 2021 01:10:50 PM UTC admin N/A
2021_08_26_12_17_48 reboot Thu 26 Aug 2021 12:16:36 PM UTC admin N/A
Syslogs
Aug 26 14:08:39.494124 str2-z9332f-01 INFO determine-reboot-cause: Platform api returns reboot cause Non-Hardware, None
Aug 26 14:08:39.494340 str2-z9332f-01 INFO determine-reboot-cause: Platform api indicates reboot cause Non-Hardware
Aug 26 14:08:39.494484 str2-z9332f-01 INFO determine-reboot-cause: /host/reboot-cause/reboot-cause.txt indicates the reboot cause: Unknown
Steps to reproduce the issue:
Powercycle device and check reboot-cause using 'show reboot-cause' or
Run platform_tests/test_reboot.py::test_power_off_reboot
Describe the results you received:
Reboot-cause shows as "Unknown" after power-cycle
Describe the results you expected:
Reboot-cause should be "Power Loss"
Output of show version:
SONiC Software Version: SONiC.20201231.19
Distribution: Debian 10.10
Kernel: 4.19.0-12-2-amd64
Build commit: caa4763e25
Build date: Wed Aug 25 13:23:00 UTC 2021
Built by: AzDevOps@sonic-int-build-workers-00032R
Platform: x86_64-dellemc_z9332f_d1508-r0
HwSKU: DellEMC-Z9332f-O32
ASIC: broadcom
ASIC Count: 1
Serial Number: TH04CN21CET0004K0214
Uptime: 19:04:22 up 4:55, 3 users, load average: 0.45, 0.51, 0.57
Output of show techsupport:
(paste your output here or download and attach the file here )
Additional information you deem important (e.g. issue happens only occasionally):
@tjchadaga, @sujinmkang Can you please paste the output of "cat /var/log/firmware_versions"?.
If the platform components firmware are not updated, requesting you to upgrade it and rerun the tests.
@tjchadaga, @sujinmkang Can you please paste the output of "cat /var/log/firmware_versions"?.
If the platform components firmware are not updated, requesting you to upgrade it and rerun the tests.
@aravindmani-1 - Thanks, after firmware upgrade, the status is now " Hardware - Other (Power on reset)" instead of Unknown.
This is the version:
cat /var/log/firmware_versions
BIOS: 2.0.4
FPGA: 0.6
BMC: 1.3
Baseboard CPLD: 9
Switch CPLD 1: 1
Switch CPLD 2: 1
The test case still fails since its looking for "power loss". I guess the script can be updated to handle this.
Why I did it
Power cycle test case fails for Z9332f in sonic-mgmt framework(#8605).
How I did it
Modified the platform API to return expected strings.
How to verify it
Power cycle the device and verify the reboot reason.
Run sonic-mgmt test_reboot script.
Why I did it
Power cycle test case fails for Z9332f in sonic-mgmt framework(#8605).
How I did it
Modified the platform API to return expected strings.
How to verify it
Power cycle the device and verify the reboot reason.
Run sonic-mgmt test_reboot script.
Description
Platform API is not recognizing reboot-cause after powercycle of 9332.
Syslogs
Steps to reproduce the issue:
Describe the results you received:
Reboot-cause shows as "Unknown" after power-cycle
Describe the results you expected:
Reboot-cause should be "Power Loss"
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
syslog.86.gz
syslog.87.gz
The text was updated successfully, but these errors were encountered: