[Agent] macOS Agent goes unhealthy due to chown call made to Endpoint log file during start up

[EricDavisX]

I found that my mac Agent worked ok during a first install, with machine reboots, but after I enabled Endpoint in the policy and rebooted Endpoint was not able to connect to Agent (policy shows specifically that as a failure) and Agent goes to unhealthy state.

testing with 7.11 BC2 Agent and cloud prod deploy

here is the most recent / telling section of log file:
macos-agent-log-file.txt

UI looks like this:

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[EricDavisX]

this is merged and waiting for new 7.11 BC to pick up the changes for testing

[EricDavisX]

this issue happens on Agent start up, so you will see the failure as noted during 'Agent upgrade' tests as the Agent restarts itself, and if it is protected by Endpoint it will have this problem too (on Windows and macOS)

[EricDavisX]

this should be available in 7.11 BC3, compiled last week - tho we are still seeing some problems with our Agents not showing as healthy, consistently in our BC3 test. We have other issues open to track it tho, but I wanted to comment here.