[Security Soluton][Endpoint] Fix run_sentinelone_host dev script to retry when checking S1 agent status on VM#227067
Merged
paul-tavares merged 1 commit intoelastic:mainfrom Jul 9, 2025
Conversation
Contributor
|
Pinging @elastic/security-defend-workflows (Team:Defend Workflows) |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
|
szwarckonrad
approved these changes
Jul 9, 2025
tomsonpl
approved these changes
Jul 9, 2025
Contributor
|
Starting backport for target branches: 8.19, 9.1 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jul 9, 2025
… retry when checking S1 agent status on VM (elastic#227067) ## Summary - Add retry attempts when getting a status of the SentinelOne agent running on the host VM - It seems that it now takes the S1 a bit of time to start up, which was causing the command to get its run status to fail (see error below) Error: ``` │ERROR Error: Command failed with exit code 1: multipass exec ptavares-sentinelone-support-3876 -- sudo /opt/sentinelone/bin/sentinelctl control status │ Agent must be running in order to execute this command ``` (cherry picked from commit d7eb4a2)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jul 9, 2025
… retry when checking S1 agent status on VM (elastic#227067) ## Summary - Add retry attempts when getting a status of the SentinelOne agent running on the host VM - It seems that it now takes the S1 a bit of time to start up, which was causing the command to get its run status to fail (see error below) Error: ``` │ERROR Error: Command failed with exit code 1: multipass exec ptavares-sentinelone-support-3876 -- sudo /opt/sentinelone/bin/sentinelctl control status │ Agent must be running in order to execute this command ``` (cherry picked from commit d7eb4a2)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jul 9, 2025
…ipt to retry when checking S1 agent status on VM (#227067) (#227242) # Backport This will backport the following commits from `main` to `9.1`: - [[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM (#227067)](#227067) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Paul Tavares","email":"56442535+paul-tavares@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-07-09T12:49:14Z","message":"[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM (#227067)\n\n## Summary\n\n- Add retry attempts when getting a status of the SentinelOne agent\nrunning on the host VM\n- It seems that it now takes the S1 a bit of time to start up, which was\ncausing the command to get its run status to fail (see error below)\n\n\nError:\n\n```\n│ERROR Error: Command failed with exit code 1: multipass exec ptavares-sentinelone-support-3876 -- sudo /opt/sentinelone/bin/sentinelctl control status\n │ Agent must be running in order to execute this command\n\n```","sha":"d7eb4a217f5ebaa29093073590e8e0281a2e7d3e","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:version","v9.1.0","v8.19.0","v9.2.0"],"title":"[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM","number":227067,"url":"https://github.com/elastic/kibana/pull/227067","mergeCommit":{"message":"[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM (#227067)\n\n## Summary\n\n- Add retry attempts when getting a status of the SentinelOne agent\nrunning on the host VM\n- It seems that it now takes the S1 a bit of time to start up, which was\ncausing the command to get its run status to fail (see error below)\n\n\nError:\n\n```\n│ERROR Error: Command failed with exit code 1: multipass exec ptavares-sentinelone-support-3876 -- sudo /opt/sentinelone/bin/sentinelctl control status\n │ Agent must be running in order to execute this command\n\n```","sha":"d7eb4a217f5ebaa29093073590e8e0281a2e7d3e"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/227067","number":227067,"mergeCommit":{"message":"[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM (#227067)\n\n## Summary\n\n- Add retry attempts when getting a status of the SentinelOne agent\nrunning on the host VM\n- It seems that it now takes the S1 a bit of time to start up, which was\ncausing the command to get its run status to fail (see error below)\n\n\nError:\n\n```\n│ERROR Error: Command failed with exit code 1: multipass exec ptavares-sentinelone-support-3876 -- sudo /opt/sentinelone/bin/sentinelctl control status\n │ Agent must be running in order to execute this command\n\n```","sha":"d7eb4a217f5ebaa29093073590e8e0281a2e7d3e"}}]}] BACKPORT--> Co-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Jul 9, 2025
…ript to retry when checking S1 agent status on VM (#227067) (#227241) # Backport This will backport the following commits from `main` to `8.19`: - [[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM (#227067)](#227067) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Paul Tavares","email":"56442535+paul-tavares@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-07-09T12:49:14Z","message":"[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM (#227067)\n\n## Summary\n\n- Add retry attempts when getting a status of the SentinelOne agent\nrunning on the host VM\n- It seems that it now takes the S1 a bit of time to start up, which was\ncausing the command to get its run status to fail (see error below)\n\n\nError:\n\n```\n│ERROR Error: Command failed with exit code 1: multipass exec ptavares-sentinelone-support-3876 -- sudo /opt/sentinelone/bin/sentinelctl control status\n │ Agent must be running in order to execute this command\n\n```","sha":"d7eb4a217f5ebaa29093073590e8e0281a2e7d3e","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:version","v9.1.0","v8.19.0","v9.2.0"],"title":"[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM","number":227067,"url":"https://github.com/elastic/kibana/pull/227067","mergeCommit":{"message":"[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM (#227067)\n\n## Summary\n\n- Add retry attempts when getting a status of the SentinelOne agent\nrunning on the host VM\n- It seems that it now takes the S1 a bit of time to start up, which was\ncausing the command to get its run status to fail (see error below)\n\n\nError:\n\n```\n│ERROR Error: Command failed with exit code 1: multipass exec ptavares-sentinelone-support-3876 -- sudo /opt/sentinelone/bin/sentinelctl control status\n │ Agent must be running in order to execute this command\n\n```","sha":"d7eb4a217f5ebaa29093073590e8e0281a2e7d3e"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/227067","number":227067,"mergeCommit":{"message":"[Security Soluton][Endpoint] Fix `run_sentinelone_host` dev script to retry when checking S1 agent status on VM (#227067)\n\n## Summary\n\n- Add retry attempts when getting a status of the SentinelOne agent\nrunning on the host VM\n- It seems that it now takes the S1 a bit of time to start up, which was\ncausing the command to get its run status to fail (see error below)\n\n\nError:\n\n```\n│ERROR Error: Command failed with exit code 1: multipass exec ptavares-sentinelone-support-3876 -- sudo /opt/sentinelone/bin/sentinelctl control status\n │ Agent must be running in order to execute this command\n\n```","sha":"d7eb4a217f5ebaa29093073590e8e0281a2e7d3e"}}]}] BACKPORT--> Co-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>
kertal
pushed a commit
to kertal/kibana
that referenced
this pull request
Jul 25, 2025
… retry when checking S1 agent status on VM (elastic#227067) ## Summary - Add retry attempts when getting a status of the SentinelOne agent running on the host VM - It seems that it now takes the S1 a bit of time to start up, which was causing the command to get its run status to fail (see error below) Error: ``` │ERROR Error: Command failed with exit code 1: multipass exec ptavares-sentinelone-support-3876 -- sudo /opt/sentinelone/bin/sentinelctl control status │ Agent must be running in order to execute this command ```
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Summary
Error: