Systems.Eventlog.Test Association: Unable to use the callout-test of the debug tarball.

[allen810118]

Hi, I encountered an error while testing Testcase: Create Test Error Callout And Verify. When the robot tries to Create Test Error With Callout, it cannot find callout-test. (I have ensured that the debug tarball has been correctly installed in the /tmp directory of the target machine.)

And I also independently executed callout-test on the target machine and obtained the same situation：No such file or directory Is this problem occurring because the openbmc version I am using is too outdated?

My test configuration is as follows: OpenBMC version follow 2.12.0 The source of the debug tarball file is witherspoon prebuild The command I used during testing was: #robot -v OPENBMC_HOST:${IP_ADDR} -i Create_Test_Error_Callout_And_Verify -v DEBUG_TARBALL_PATH:redfish/systems/eventlog/obmc-phosphor-debug-tarball-witherspoon.tar.xz redfish/systems/eventlog/test_association.robot

[gkeishin]

To get the community tar ball..

1. Go to https://jenkins.openbmc.org/job/latest-master/
2. Choose any of the target platform build accordingly
3. Navigate to the page where the images / tars are available.. Example fro Target Witherspoon https://jenkins.openbmc.org/job/latest-master/label=docker-builder,target=witherspoon/947/artifact/openbmc/build/tmp/deploy/images/witherspoon/
4. Download tar ball for that target .. Example: ```obmc-phosphor-debug-tarball-witherspoon-20231108025050.tar.xz

   
   5,   pass the param when executing the test   
   ```-v DEBUG_TARBALL_PATH:<tarball path>```

That should do, Hope that helps

[allen810118]

To get the community tar ball..

1. Go to https://jenkins.openbmc.org/job/latest-master/
2. Choose any of the target platform build accordingly
3. Navigate to the page where the images / tars are available.. Example fro Target Witherspoon https://jenkins.openbmc.org/job/latest-master/label=docker-builder,target=witherspoon/947/artifact/openbmc/build/tmp/deploy/images/witherspoon/
4. Download tar ball for that target .. Example: ```obmc-phosphor-debug-tarball-witherspoon-20231108025050.tar.xz

5,   pass the param when executing the test   
```-v DEBUG_TARBALL_PATH:<tarball path>```

That should do, Hope that helps

I still can't execute "callout-test" using the provided tarball file. Whenever I call out to "callout-test", it always prompts (Whether it is in the console or through a robot file ): No such file or directory

[allen810118]

To get the community tar ball..

1. Go to https://jenkins.openbmc.org/job/latest-master/
2. Choose any of the target platform build accordingly
3. Navigate to the page where the images / tars are available.. Example fro Target Witherspoon https://jenkins.openbmc.org/job/latest-master/label=docker-builder,target=witherspoon/947/artifact/openbmc/build/tmp/deploy/images/witherspoon/
4. Download tar ball for that target .. Example: ```obmc-phosphor-debug-tarball-witherspoon-20231108025050.tar.xz

5,   pass the param when executing the test   
```-v DEBUG_TARBALL_PATH:<tarball path>```

That should do, Hope that helps

I still can't execute "callout-test" using the provided tarball file. Whenever I call out to "callout-test", it always prompts (Whether it is in the console or through a robot file ): No such file or directory

Supplementary information: Report of Robot testing

OpenBMC version follow 2.12.0 openbmc-test-automation follow v3.0-stable

[gkeishin]

root@xx.xx.xx.xx:~# cd /tmp/tarball/
root@xx.xx.xx.xx:/tmp/tarball# pwd
/tmp/tarball
root@xx.xx.xx.xx:/tmp/tarball# ls bin/callout-test
bin/callout-test
root@xx.xx.xx.xx:/tmp/tarball#

root@xx.xx.xx.xx:/tmp/tarball# /tmp/tarball/bin/callout-test /sys/devices/platform/gpio-fsi/fsi0/slave@00:00/raw
root@xx.xx.xx.xx:/tmp/tarball# Nov 09 01:33:52 xx.xx.xx.xx callout-test[1153]: This is test error TestCallout
Nov 09 01:33:52 xx.xx.xx.xx systemd-journald[124]: Forwarding to syslog missed 1 messages.
Nov 09 01:33:52 xx.xx.xx.xx callout-test[1153]: method is deprecated, use commit() with exception type
Nov 09 01:33:52 xx.xx.xx.xx systemd[1]: systemd-journald.service: Sent signal SIGRTMIN+1 to main process 124 (systemd-journal) on client request.
Nov 09 01:33:52 xx.xx.xx.xx phosphor-fru-fault-monitor[453]: /xyz/openbmc_project/logging/entry/1 created

***Variables***
${target_device_path}  /sys/devices/platform/gpio-fsi/fsi0/slave@00:00/raw

This is the target path.. so you are using different target, so probably you might need to talk to Developer if you are trying something else where it works.. The above target is working as posted with logs there.

and also use the latest master code for testing in general. its been quite some time and many changes have gone in.. and we are planning to branch out this year-end v4 version ahead..

[allen810118]

The test tarball I am using is obmc-phosphor-debug-tarball-witherspoon-20231108025050.tar.xz OpenBMC version follow 2.12.0 openbmc-test-automation follow v3.0-stable

and I operated in the Console according to the above method. root@allen:~# cd /tmp/tarball/ root@allen:/tmp/tarball# pwd /tmp/tarball root@allen:/tmp/tarball# ls bin/callout-test bin/callout-test root@allen:/tmp/tarball/bin# /tmp/tarball/bin/callout-test /sys/devices/platform/gpio-fsi/fsi0/slave@00:00/raw -sh: /tmp/tarball/bin/callout-test: No such file or directory

Test results show: No such file or directory Is this problem caused by the version too outdated of OpenBMC?

[gkeishin]

Not sure.. if you scp the tarball to BMC and login to BMC Shell and execute it, it should work and it wont hurt to update the OpenBMC version too on your BMC.

[gkeishin]

@allen810118 Found anything else working for you ?