Move the context cancelled error message into a debug statement

[ph]

This code improve the error reporting when Elastic Agent is stopped
through the pass context. This move the state reporting closer to the
execution of the request. Error related to the request would still be
logged as error and will change the internal state to non healthy.

Fixes: #154

[mergify]

This pull request does not have a backport label. Could you fix it @ph? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-03-16T16:58:31.489+0000

• Duration: 31 min 29 sec

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[ph]

@narph I believe the ci:end-to-end label would trigger a CI Job, but I don't see the end to end test name in the list of job run for this PR.

[narph]

run end-to-end tests

[narph]

@narph I believe the ci:end-to-end label would trigger a CI Job, but I don't see the end to end test name in the list of job run for this PR.

it requires to run a build to enable it, looks like my comment triggered the tests

[ph]

/test

[ph]

let's see if a manual trigger show this.

[ph]

@narph @v1v seems we cannot retrieve the filebeat artifacts?

[ph]

Probably because of the artifact api issues.

[v1v]

@narph @v1v seems we cannot retrieve the filebeat artifacts?

Maybe the release platform team might know if something is down in the artifacts-api?

[narph]

@narph @v1v seems we cannot retrieve the filebeat artifacts?

Maybe the release platform team might know if something is down in the artifacts-api?

Just saw an email regarding an outage (redacted the issue which points to an internal repo)

[ph]

/test

[ph]

Yes this is probably due to the artifact outage.