Skip to content

Test Design of revenlog python version

tingtli edited this page Mar 28, 2018 · 3 revisions

Test Design of reventlog python version

Introduction

This document provides an overview of test of command reventlog that is conducted on the IBM Witherspoon Physical Machine. This test plan is intended for the use of xCAT FVT team.

The test is against xCAT version 2.14. The build of xCAT will be picked up from the xcat.org

Overview of xCAT FVT

Test Software Requirements

Operating System :Red Hat Enterprise Linux Server release 7.5

Other Softwares

xCAT 2.14

Test Hardware Requirements

MN: any machines with latest xcat installed
CN: Witherspoon node (p9)

xCAT Test Detail Section

Test environment preparation

Test cases

Automation cases

We have some reventlog automation cases in file cases0 under /opt/xcat/share/xcat/tools/autotest/testcase/reventlog. After you install xcat-test, you will find the file.

[root@briggs01 reventlog]# pwd
/opt/xcat/share/xcat/tools/autotest/testcase/reventlog
[root@briggs01 reventlog]# ls
cases0

The steps to run automation cases.

  1. Install xcat-test on your testing nodes
  2. Define node. The node's definition should have bmc's ip. BMC should work correctly.
  3. create reventlog cases bundle file by yourself.
[root@briggs01 bundle]# pwd
/opt/xcat/share/xcat/tools/autotest/bundle
[root@briggs01 bundle]# cat reventlog.bundle
[root@briggs01 bundle]# cat reventlog.bundle
reventlog_null
reventlog_all
reventlog_clear
reventlog_numofentries
reventlog_s_openbmc
  1. Run following commands to start your test.
[root@briggs01 testcase]# XCATTEST_CN=mid05tor12cn05 xcattest -b reventlog.bundle
  1. Check the result under following directory
[root@briggs01 result]# pwd
/opt/xcat/share/xcat/tools/autotest/result
[root@briggs01 result]# vi failedcases.20180201192605

Manually cases

The test cases is given according to the reventlog' help information for machines managed by openbmc.

[root@briggs01 ~]# reventlog -h
Usage: reventlog <noderange> [all [-s]|clear|<number of entries to retrieve> [-s]] [-V|--verbose]
       reventlog <noderange> [resolved={<id list>|LED}]
       reventlog [-h|--help|-v|--version]
Some cases list

[root@briggs01 ~]# reventlog -h Usage: reventlog [all [-s]|clear| [-s]] [-V|--verbose] reventlog [resolved={|LED}] reventlog [-h|--help|-v|--version]

[root@briggs01 ~]# reventlog --help Usage: reventlog [all [-s]|clear| [-s]] [-V|--verbose] reventlog [resolved={|LED}] reventlog [-h|--help|-v|--version]

[root@briggs01 ~]# reventlog -v Version 2.14 (git commit bc1de0529c90356fe23753fe3fd9d593ff99b461, built Tue Mar 27 06:15:43 EDT 2018)

[root@briggs01 ~]# reventlog --version Version 2.14 (git commit bc1de0529c90356fe23753fe3fd9d593ff99b461, built Tue Mar 27 06:15:43 EDT 2018)

[root@briggs01 ~]# reventlog mid05tor12cn13 mid05tor12cn13: 03/15/2018 13:11:56 [1]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 0 mid05tor12cn13: 03/15/2018 13:12:41 [2]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 5510), Resolved: 0 mid05tor12cn13: 03/15/2018 13:13:34 [3]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 0 mid05tor12cn13: 03/15/2018 13:14:19 [4]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 6159), Resolved: 0 mid05tor12cn13: 03/15/2018 13:15:11 [5]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 0 mid05tor12cn13: 03/15/2018 13:15:56 [6]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 6791), Resolved: 0 mid05tor12cn13: 03/15/2018 13:16:42 [7]: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 6820), Resolved: 0

[root@briggs01 ~]# reventlog mid05tor12cn13 2 mid05tor12cn13: 03/15/2018 13:15:56 [6]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 6791), Resolved: 0 mid05tor12cn13: 03/15/2018 13:16:42 [7]: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 6820), Resolved: 0

[root@briggs01 ~]# reventlog mid05tor12cn13 2 -s Error: Agent exited unexpectedly. See /var/log/xcat/agent.log for details. To revert to Perl framework: chdef -t site clustersite openbmcperl=ALL [root@briggs01 ~]# echo $? "runbootscripts","1",, 1 [root@briggs01 ~]# tail /var/log/xcat/agent.log /opt/xcat/lib/python/agent/hwctl/executor/openbmc_bmcconfig.py:13: RuntimeWarning: Patching more than once will result in the union of all True parameters being patched monkey.patch_all() Usage: reventlog [-V|--verbose] resolved <id_list> reventlog [-V|--verbose] clear "runbootscripts","1",, reventlog [-V|--verbose] list <number_of_records> Exception KeyError: KeyError(1100310128752,) in <module 'threading' from '/usr/lib64/python2.7/threading.pyc'> ignored

[root@briggs01 ~]# reventlog mid05tor12cn13 all mid05tor12cn13: 03/15/2018 13:11:56 [1]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 0 mid05tor12cn13: 03/15/2018 13:12:41 [2]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 5510), Resolved: 0 mid05tor12cn13: 03/15/2018 13:13:34 [3]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 0 mid05tor12cn13: 03/15/2018 13:14:19 [4]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 6159), Resolved: 0 mid05tor12cn13: 03/15/2018 13:15:11 [5]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 0 mid05tor12cn13: 03/15/2018 13:15:56 [6]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 6791), Resolved: 0 mid05tor12cn13: 03/15/2018 13:16:42 [7]: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 6820), Resolved: 0

[root@briggs01 ~]# reventlog mid05tor12cn13 all -s Error: Agent exited unexpectedly. See /var/log/xcat/agent.log for details. To revert to Perl framework: chdef -t site clustersite openbmcperl=ALL

[root@briggs01 ~]# reventlog mid05tor12cn15 clear mid05tor12cn15: Logs cleared [root@briggs01 ~]# reventlog mid05tor12cn15 all mid05tor12cn15: No attributes returned from the BMC.

[root@briggs01 ~]# reventlog mid05tor12cn13 resolved=1 Attempting to resolve the following log entries: 1... mid05tor12cn13: Resolved 1 [root@briggs01 ~]# echo $? 0 [root@briggs01 ~]# reventlog mid05tor12cn13 1 mid05tor12cn13: 03/15/2018 13:16:42 [7]: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 6820), Resolved: 0

[root@briggs01 ~]# reventlog mid05tor12cn13 all mid05tor12cn13: 03/15/2018 13:11:56 [1]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 1 mid05tor12cn13: 03/15/2018 13:12:41 [2]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 5510), Resolved: 0 mid05tor12cn13: 03/15/2018 13:13:34 [3]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 0 mid05tor12cn13: 03/15/2018 13:14:19 [4]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 6159), Resolved: 0 mid05tor12cn13: 03/15/2018 13:15:11 [5]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 0 mid05tor12cn13: 03/15/2018 13:15:56 [6]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 6791), Resolved: 0 mid05tor12cn13: 03/15/2018 13:16:42 [7]: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 6820), Resolved: 0

[root@briggs01 ~]# reventlog mid05tor12cn13 resolved=1,3,7 Attempting to resolve the following log entries: 1,3,7... mid05tor12cn13: Resolved 3 mid05tor12cn13: Resolved 7 [root@briggs01 ~]# reventlog mid05tor12cn13 all mid05tor12cn13: 03/15/2018 13:11:56 [1]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 1 mid05tor12cn13: 03/15/2018 13:12:41 [2]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 5510), Resolved: 0 mid05tor12cn13: 03/15/2018 13:13:34 [3]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 1 mid05tor12cn13: 03/15/2018 13:14:19 [4]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 6159), Resolved: 0 mid05tor12cn13: 03/15/2018 13:15:11 [5]: Firmware/Software Failure, (Warning) An internal failure has occurred while performing an operation. (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 1324), Resolved: 0 mid05tor12cn13: 03/15/2018 13:15:56 [6]: Firmware/Software Failure, (Critical) Hostboot has become unresponsive (AffectedSubsystem: Systems Management - Core / Virtual Appliance, PID: 6791), Resolved: 0 mid05tor12cn13: 03/15/2018 13:16:42 [7]: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 6820), Resolved: 1

[root@briggs01 ~]# reventlog mid05tor12cn13 resolved=LED Attempting to resolve the following log entries: LED... mid05tor12cn13: No event log entries needed to be resolved [root@briggs01 ~]# echo $? 0

[root@briggs01 ~]# reventlog mid05tor12cn13 all aaa Error: Agent exited unexpectedly. See /var/log/xcat/agent.log for details. To revert to Perl framework: chdef -t site clustersite openbmcperl=ALL [root@briggs01 ~]# echo $? 1 [root@briggs01 ~]# tail -f /var/log/xcat/agent.log monkey.patch_all() /usr/lib/python2.7/site-packages/urllib3/connectionpool.py:769: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html InsecureRequestWarning) /opt/xcat/lib/python/agent/hwctl/executor/openbmc_bmcconfig.py:13: RuntimeWarning: Patching more than once will result in the union of all True parameters being patched monkey.patch_all() Usage: reventlog [-V|--verbose] resolved <id_list> reventlog [-V|--verbose] clear reventlog [-V|--verbose] list <number_of_records> Exception KeyError: KeyError(1099935590512,) in <module 'threading' from '/usr/lib64/python2.7/threading.pyc'> ignored

^C

News

History

  • Oct 22, 2010: xCAT 2.5 released.
  • Apr 30, 2010: xCAT 2.4 is released.
  • Oct 31, 2009: xCAT 2.3 released. xCAT's 10 year anniversary!
  • Apr 16, 2009: xCAT 2.2 released.
  • Oct 31, 2008: xCAT 2.1 released.
  • Sep 12, 2008: Support for xCAT 2 can now be purchased!
  • June 9, 2008: xCAT breaths life into (at the time) the fastest supercomputer on the planet
  • May 30, 2008: xCAT 2.0 for Linux officially released!
  • Oct 31, 2007: IBM open sources xCAT 2.0 to allow collaboration among all of the xCAT users.
  • Oct 31, 1999: xCAT 1.0 is born!
    xCAT started out as a project in IBM developed by Egan Ford. It was quickly adopted by customers and IBM manufacturing sites to rapidly deploy clusters.
Clone this wiki locally