-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve starting ipmi_sim program #9378
Improve starting ipmi_sim program #9378
Conversation
👋 Hello! Thanks for contributing to our project. If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code. Reference tests: KNOWN ISSUES Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience. For more tips on troubleshooting, see the troubleshooting guide. Happy hacking! |
Also, take a look to the GH tests before merging please. Actually it might not let you merge otherwise :) |
423018f
to
ce55123
Compare
Improve killing fake_ipmi_host.sh
ce55123
to
297f81f
Compare
8da9611
to
4fddd33
Compare
c382c68
to
ee07b2b
Compare
Update
I have this issue:
So I ignore the errors for
get_target('server').run('pkill --full fake_ipmi_host.sh')
Context
If one of the IPMI Power management features is failing, it will keep
ipmi_sim
process running. The next feature will try to start again thisipmi_sim
process. In this situation, the commandipmi_sim -n < /dev/null > /dev/null &
will be executed and wait for the previous process to stop ( nothing will stop the process ). The command will not return any code and the ssh connection will die. This situation will not be detected by the ssh timeout and the testsuite will stay stuck forever at this stage.What does this PR change?
Use nohup command to start the service. This command will return immediately a result even if the process is already running.
Improve the IPMI mocking cleanup. From my test,
pkill fake_ipmi_host.sh || :
was not killing successfullyfake_ipmi_host
. ( detected by rerunning several time the same features. )GUI diff
No difference.
Documentation
No documentation needed: only internal and user invisible changes
DONE
Test coverage
ℹ️ If a major new functionality is added, it is strongly recommended that tests for the new functionality are added to the Cucumber test suite
No tests: already covered
DONE
Links
Port:
5.0: https://github.com/SUSE/spacewalk/pull/25807
4.3: https://github.com/SUSE/spacewalk/pull/25808
Issue:
DONE
Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:
If you uncheck the checkbox after the PR is created, you will need to re-run
changelog_test
(see below)Re-run a test
If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:
Before you merge
Check How to branch and merge properly!