Robot Framework 7.0 changes

Update robot code syntax overall in the repo

Changes:
- Update the requirement.txt package version for robot
- The '[Return]' setting is deprecated.
Use the

Robot Framework 7.0 changes

Update robot code syntax overall in the repo

Changes:
- Update the requirement.txt package version for robot
- The '[Return]' setting is deprecated.
Use the 'RETURN' statement instead.
- Singular section headers like '*** Test Case ***'
are deprecated. Use plural format like
'*** Test Cases ***' instead.
- Singular section headers like '*** Variable ***'
are deprecated

Tested:
- Ran from sandbox with the version
$ robot --version
Robot Framework 7.0 (Python 3.10.12 on linux)

and also tested on latest python version

Robot Framework 7.0 (Python 3.11.9 on linux)

Change-Id: I54e85f9d799556c63b9a39f79483f83e9b980768
Signed-off-by: George Keishing <gkeishin@in.ibm.com>

show more ...

Robotframework request package upgrade changes

Current working package version
robotframework-requests 0.7.2

To Test:
pip3 install robotframework-requests -U
or

Robotframework request package upgrade changes

Current working package version
robotframework-requests 0.7.2

To Test:
pip3 install robotframework-requests -U
or
# Once this commit is merged.
pip3 install -r requirements.txt

Version latest:
robotframework-requests 0.9.3

Refer Documentation:
https://marketsquare.github.io/robotframework-requests/doc/RequestsLibrary.html

What is not changed:
- The test cases under directory tests/ is not modified and is
deprecated but you can continue using it with older package
and configuration using

git clone -b v3.0-stable https://github.com/openbmc/openbmc-test-automation

Tested:
Upstream HW_CI test list, firmware code update and few other
test suite like ipmi, certificate, dumps, ffdc and redfish
test suites.

Note: I have not tested end to end, so it is likely there could be
grey areas where it could fail but should be minor w.r.t
response data format.

Resolves: openbmc/openbmc-test-automation#2105

Change-Id: Ie03b25ff88948bcccb09e9d82f8da86e28c92697
Signed-off-by: George Keishing <gkeishin@in.ibm.com>

show more ...

Fix missing requirement for GUI test

Signed-off-by: Troy Lee <troy_lee@aspeedtech.com>
Change-Id: Ib71d67d2d52c591da8c154a595c0feefc0ed22dd

ffdc: Add base infrastructure to support redfish protocol.

- Set 1: Initial commit for review. Add -t BMC_GET for redfish.
- Set 2: Add new CLI option --remote_protocol (-rp).
Defaul

ffdc: Add base infrastructure to support redfish protocol.

- Set 1: Initial commit for review. Add -t BMC_GET for redfish.
- Set 2: Add new CLI option --remote_protocol (-rp).
Default: ALL available.
- Set 3: Enhance messaging for Refish path.

Test:
- All types to OpenBMC's, RHEL, Ubuntu and AIX.
- Regression test to OpenBMC's, RHEL, Ubuntu and AIX.

Signed-off-by: Peter D Phan <peterp@us.ibm.com>
Change-Id: I969a923b49cc38314cdc194a9e6de8acc3f89fdb

show more ...

ffdc: Add standalone FFDC collector script

- Set 1: 1st Pass: default to OpenBMC and SSH.
- Set 2: Remove trailing spaces.
- Set 3: Remove trailing spaces - part 2.
- Set 4: Addr

ffdc: Add standalone FFDC collector script

- Set 1: 1st Pass: default to OpenBMC and SSH.
- Set 2: Remove trailing spaces.
- Set 3: Remove trailing spaces - part 2.
- Set 4: Address pycodestyle,
openbmc Python Coding Guidelines and review feedback issues.
- Set 5: more correction to meet pycodestyle.
- Set 6: Address review comments. Test scenarios were (re)executed.
- Set 7: Relocate all FFDC Collector files in ffdc/ dir.
Test scenarios were (re)executed with newly relocated files.
- Set 8: Make script progress, status more informative.
Add error handling, making error message more informative.
Add test for error scenarios.

Tested: 7 cli scenarios
(1) python3 <sandbox>/openbmc-test-automation/ffdc/collect_ffdc.py \
-h <> -u <> -p <> -f <sandbox>/openbmc-test-automation/ffdc/ffdc_config.yaml

(2) cd <sandbox>/openbmc-test-automation/ffdc
python3 collect_ffdc.py -h <> -u <> -p <>

(3) export OPENBMC_HOST=<>
export OPENBMC_USERNAME=<>
export OPENBMC_PASSWORD=<>
cd <sandbox>/openbmc-test-automation/ffdc
python3 collect_ffdc.py

(4) python3 collect_ffdc.py -h <invalid host>
(5) python3 collect_ffdc.py -u <invalid userid>
(6) python3 collect_ffdc.py -p <invalid password>
(7) python3 collect_ffdc.py -l <path with no access (/var, /opt)>

Change-Id: Ia26630168856341e749ce73b5cced831fc470219
Signed-off-by: Peter D Phan <peterp@us.ibm.com>

show more ...

Bump paramiko to support diffie-hellman-group14-sha256 key exchange algo

This bump paramiko to 2.5.0, the first released version to support
diffie-hellman-group14-sha256 key exchange alg

Bump paramiko to support diffie-hellman-group14-sha256 key exchange algo

This bump paramiko to 2.5.0, the first released version to support
diffie-hellman-group14-sha256 key exchange algorithm. It is needed to
work with current OpenBMC since c347ece05a7fdbf50d76cb136b9ed45caed333f6
poky commit disabled diffie-hellman-group14-sha1 in dropbear (for
security reasons) and so no common kex algos were left.

Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Change-Id: I72f99ffcad6ef0f2cde8a7904080388465ed03b7

show more ...

Update minimal required version for the 'paramiko' package

Versions below 2.1.0 fail with the error
"Incompatible ssh peer (no acceptable kex algorithm)".

And versions below 2.3

Update minimal required version for the 'paramiko' package

Versions below 2.1.0 fail with the error
"Incompatible ssh peer (no acceptable kex algorithm)".

And versions below 2.3.2 fail with the Python versions above 3.7
because of the 'async' variable bug:
https://github.com/paramiko/paramiko/issues/1108

Therefore constrain minimal paramiko version to 2.3.2

Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Ia47dd0d82a916fc5e5fc440cd2b79607c892265a

show more ...

Constrain 'robotframework-requests' to versions <0.8.0

Robotframework request API was changed in a version 0.8.0.
It is not possible to use the newest version with the current
openbm

Constrain 'robotframework-requests' to versions <0.8.0

Robotframework request API was changed in a version 0.8.0.
It is not possible to use the newest version with the current
openbmc-test-automation codebase.
Therefore constrain 'robotframework-requests' version to <0.8.0.

Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I7485e8a86ee4b94704032f495309e05b53f6b379

show more ...

Bump paramiko from 2.0.2 to 2.0.9

Reference https://github.com/openbmc/openbmc-test-automation/pull/1966

Change-Id: I7b98021eb970601e8b438f6e39ad16b1f757c303
Signed-off-by: Geor

Bump paramiko from 2.0.2 to 2.0.9

Reference https://github.com/openbmc/openbmc-test-automation/pull/1966

Change-Id: I7b98021eb970601e8b438f6e39ad16b1f757c303
Signed-off-by: George Keishing <gkeishin@in.ibm.com>

show more ...

Addition in requirements.txt

Change-Id: Ib1581d5f54b0b4ddb60f0d333f707d43bc23598e
Signed-off-by: Sridevi Ramesh <sridevra@in.ibm.com>

Paramiko dependencies for robotframework SSH

tox doesn't resolves the python package dependencies and SSH
library from robot framework does need paramiko explicitly

sudo pip sho

Paramiko dependencies for robotframework SSH

tox doesn't resolves the python package dependencies and SSH
library from robot framework does need paramiko explicitly

sudo pip show robotframework-sshlibrary
Name: robotframework-sshlibrary
Version: 2.1.2
Summary: Robot Framework test library for SSH and SFTP
Home-page: https://github.com/robotframework/SSHLibrary
Author: Robot Framework Developers
Author-email: robotframework@gmail.com
License: Apache License 2.0
Location: /usr/local/lib/python2.7/dist-packages
Requires: robotframework, paramiko

Resolves openbmc/openbmc#878

Change-Id: I314f92b56160a622a671e92c020b68086ae32072
Signed-off-by: George Keishing <gkeishin@in.ibm.com>

show more ...

Port suite from mkumatag personal repo w/o history

All these files came from https://github.com/mkumatag/openbmc-automation
The decision to remove the commit history was because most of

Port suite from mkumatag personal repo w/o history

All these files came from https://github.com/mkumatag/openbmc-automation
The decision to remove the commit history was because most of the 122
commits did not follow commit comment AND content best practices.
The ability to remove the commit history was possible because all
contributors where from the same company (IBM) making the coordination /
notification/acceptence easy. See all the gory details about the
first try to commit with history here...
https://github.com/openbmc/openbmc-test-automation/pull/1

This suite of tests will run against an OpenBMC based server. It will
run good/bad path testing against the REST interface. There are tests
that will also run ipmitool on the victim BMC too.

If you want to support a new system in to the suite you should only
have to edit two files...
data/<system>.py
tox.ini

The README.md contains details on how to setup for the first time along
with how to execute the test suite

NOTE: some test cases require tools that do not exist on the system.
Currently the ipmitool is needed and if you do not manually copy / link
it in to the tools directory some suites will fail.

show more ...