-
Notifications
You must be signed in to change notification settings - Fork 165
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
mantle/platform: allow systemctl is-system-running
nonzero exit codes
#3487
Conversation
The `CheckMachine()` call tolerates `systemctl is-system-running` returning e.g. `starting` and `initializing` in addition to the usual `running`. But by design, the command returns a nonzero exit code in those cases. Since we're explicitly checking the output string against the acceptable states, just ignore the command exit code so that we don't fail if the system is still starting. Prep for adding a test in which we expect the system to still be `starting`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/retest |
In coreos/coreos-assembler#3487 we are changing the `sshChecker` in `CheckMachine()` to return earlier in the `starting` and `initializing` states. This means the kola test code might start to run earlier and we may need to wait longer here.
In coreos/coreos-assembler#3487 we are changing the `sshChecker` in `CheckMachine()` to return earlier in the `starting` and `initializing` states. This means the kola test code might start to run earlier and we may need to wait longer here.
/retest |
/retest |
/cherrypick rhcos-4.13 |
@travier: new pull request created: #3497 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
In coreos/coreos-assembler#3487 we are changing the `sshChecker` in `CheckMachine()` to return earlier in the `starting` and `initializing` states. This means the kola test code might start to run earlier and we may need to wait longer here. (cherry picked from commit 3952477)
In coreos/coreos-assembler#3487 we are changing the `sshChecker` in `CheckMachine()` to return earlier in the `starting` and `initializing` states. This means the kola test code might start to run earlier and we may need to wait longer here. (cherry picked from commit 3952477)
In coreos/coreos-assembler#3487 we are changing the `sshChecker` in `CheckMachine()` to return earlier in the `starting` and `initializing` states. This means the kola test code might start to run earlier and we may need to wait longer here.
In coreos/coreos-assembler#3487 we are changing the `sshChecker` in `CheckMachine()` to return earlier in the `starting` and `initializing` states. This means the kola test code might start to run earlier and we may need to wait longer here.
The
CheckMachine()
call toleratessystemctl is-system-running
returning e.g.starting
andinitializing
in addition to the usualrunning
. But by design, the command returns a nonzero exit code in those cases.Since we're explicitly checking the output string against the acceptable states, just ignore the command exit code so that we don't fail if the system is still starting.
Prep for adding a test in which we expect the system to still be
starting
.