op-test icon indicating copy to clipboard operation
op-test copied to clipboard

Adding HtxBootme test on OpTest

Open TasmiyaNalatwad opened this issue 11 months ago • 2 comments

The test is performed in below manner

  1. Starts Htx workload on mdt.all
  2. Starts bootme which reboots the lpar every 30 minutes
  3. wait for reboot and check htxerror logs after reboot, Htx must continue without any errors
  4. Stop bootme
  5. Stop Htx workload

Param : "boot_count" must be given from machine.conf file. The param is for the number of counts the reboot cycle must happen. Default is 6

machine.conf
[op-test]
bmc_type=
bmc_ip=
bmc_username=
bmc_password=
host_ip=
host_user=
host_password=
hmc_ip=
hmc_username=
hmc_password=
system_name=
lpar_name=
time_limit=
time_unit=
boot_count=
mdt_file=
htx_rpm_link=

TasmiyaNalatwad avatar Mar 21 '24 05:03 TasmiyaNalatwad

Please find the Logs attached here [20240322112000900167.debug.log]

TasmiyaNalatwad avatar Mar 22 '24 14:03 TasmiyaNalatwad

@abdhaleegit @PraveenPenguin

  1. I have added bootme test for generic-mdt.all , Block devices and Nic devices in only one file.
  2. As we had discussed i am maintaining different classes for each test case, that can be called in the op-test command ./op-test --run testcases.OpTestHtxBootmeIO.HtxBootme_AllMdt -c machine.conf
  3. There are few more paramters to be added in the machine.conf file.
`[op-test]
bmc_type=
bmc_ip=
bmc_username==
bmc_password=
host_ip=
host_user=
host_password=
hmc_ip=
hmc_username=
hmc_password=
system_name=
lpar_name=
lpar_prof=default_profile
host_cmd_timeout=7200
git_home=/home/linux_src
machine_state=OS
time_limit=1
time_unit=m
boot_count=6
mdt_file=
htx_disks=
all=True
peer_public_ip=
peer_password=
peer_user=
htx_host_interfaces=
peer_interfaces=
htx_rpm_link=
`
  1. Attaching debug.log file for Htxbootme test on Block device to jira
  2. As we know ETA enabling Htxbootme on Nic devices is on April-25 currently i have added Htx test on the same file. Attaching debug.log file for Htx test on op-test. As the bootme code remains same and if there is no new command added in the Htxbootme for Nic device the code must work for testing Htxbootme on Nic devices after enabling bootme on it. If at all any new command is added, then that has to be included in the code.
  3. The Htx for Nic devices is running on latest changes made on HTX code what we have added on avocado as well.
  4. Attaching debug.log for Basic Htx test on Nic devices to jira

@abdhaleegit I am making use of Paramiko as i noticed pexpect is giving some time delay and sometimes getting stuck at the console prompt for infinite time. Paramiko looks much better method in that way. Also Paramiko gives various methods to check file existence, removing of file/directory and so many.

TasmiyaNalatwad avatar Apr 08 '24 15:04 TasmiyaNalatwad

Separate out commits per each logical change

abdhaleegit avatar Apr 18 '24 07:04 abdhaleegit

Separate out commits per each logical change

Done

TasmiyaNalatwad avatar Apr 18 '24 10:04 TasmiyaNalatwad

@TasmiyaNalatwad so we do not have logs for NIC bootme.. than you can split out the PR for NICbootme separately so I can merge this generic and block as this PR.. and keep open the other PR until ETA and we have tested once

@abdhaleegit Removed Nic devices from this PR as of now. After this is merged will share the separate PR for Nic devices

TasmiyaNalatwad avatar Apr 19 '24 12:04 TasmiyaNalatwad