Mute 60-sysprobe-check.sh in the absence of config

[artyom]

Closes #15187

What does this PR do?

Mutes grep: /etc/datadog-agent/system-probe.yaml: No such file or directory message coming from 60-sysprobe-check.sh in the Docker image, where such file is not present.

Motivation

See #15187

Additional Notes

Alternative solution is to build custom docker image and maintain this fix separately.

Possible Drawbacks / Trade-offs

N/a

Describe how to test/QA your changes

N/a

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• At least one team/.. label has been applied, indicating the team(s) that should QA this change.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
• If applicable, the config template has been updated.

[bits-bot]

All committers have signed the CLA.

[L3n41c]

Hi !
Thanks for your submission !

Indeed, the system-probe.yaml configuration file isn’t mandatory anymore.
Rather than completely hiding all errors, I left a suggestion to leverage an option of grep to silent only errors about nonexistent files.

[artyom]

@L3n41c thank you for your suggestion! Indeed, -s option fits much nicer — please see the updated change.

[L3n41c]

@artyom : The CircleCI seems to fail because of an authentication issue. See this link.
Could you try to sign out of CircleCI and then to log back on GitHub and then on CircleCI as suggested to see if it fixes it.

[artyom]

@L3n41c I don't have a CircleCI account. Should I create one to unblock the pipeline?

[L3n41c]

@artyom I think you may need to sign up with your GitHub account. I’m not 100% sure.

[artyom]

@L3n41c ok, I signed up to CircleCI with my GitHub account, please see if that helped. I cannot re-run the workflow myself.

[st-cyrill]

@L3n41c
I faced the same problem. I hope this pull request will be merge.
Can you help us take the next action?