Jenkinsfile.integration: use sesdev create --salt
#701
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After looking through ceph-salt logs from previous failed Jenkins runs, and also at Volker's issue which seems to be the same thing (see #700), my current suspicion is that the ceph-salt executor is correctly starting `salt -G 'ceph-salt:member' state.apply ceph-salt` but is then failing to pick up some (or all) of the event notifications, which results in it returning too soon, while `cephadm bootstrap` is still running. Assuming I'm on the right track here, let's ask `sesdev` to run that salt command directly, to remove the ceph-salt executor from the picture entirely. Signed-off-by: Tim Serong <[email protected]>
|
OK, did not expect that to fail :-/ |
In one recent CI run, the salt minion never returned and the salt minion log and cephadm.out log just stopped dead immediately after `cephadm bootstrap` was invoked. This commit collects `ps` and `journalctl` output in the hope that this will help with further debugging if we hit this issue again. Signed-off-by: Tim Serong <[email protected]>
tserong
force-pushed
the
wip-dont-use-ceph-salt-executor
branch
from
8c48614 to
ded1bde
Compare
|
The first CI run (http://see.prv.suse.net:8080/blue/organizations/jenkins/sesdev-integration/detail/PR-701/1/ failed with: So then I added ded1bde to collect more artifacts, but of course now everything is fine again - http://see.prv.suse.net:8080/blue/organizations/jenkins/sesdev-integration/detail/PR-701/4/ succeeded. There's obviously still some intermittent problem :-/ but now we'll have even more stuff for me to look at next time it fails. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After looking through ceph-salt logs from previous failed Jenkins runs, and also at Volker's issue which seems to be the same thing (see #700), my current suspicion is that the ceph-salt executor is correctly starting
salt -G 'ceph-salt:member' state.apply ceph-saltbut is then failing to pick up some (or all) of the event notifications, which results in it returning too soon, whilecephadm bootstrapis still running.Assuming I'm on the right track here, let's ask
sesdevto run that salt command directly, to remove the ceph-salt executor from the picture entirely.