Kibana version:
Kibana: 7.10.0 BC5 cloud environment

Elasticsearch version:
Elasticsearch: 7.10.0 BC5 cloud environment

Host OS and Browser version:
Linux Debian 9 , All

Original install method (e.g. download page, yum, from source, etc.):
7.10.0 BC5 cloud environment from https://cloud.elastic.co

Description
Agent goes to Offline status on reboot of Linux deb stand-alone agent enroll to Fleet

Preconditions

1. 7.10.0 BC5 Kibana cloud environment(with commit 1796b5ec8fa1e60ccea63f2e5c25ccc665b92fdc) should be available.
2. Login into the above Kibana environment with 'elastic' superuser.
3. 7.10.0 BC5 Linux amd64.deb agent package should be downloaded and installed(on Linux Debian 9) from below location:
   https://staging.elastic.co/7.10.0-b55684ff/downloads/beats/elastic-agent/elastic-agent-7.10.0-amd64.deb

Steps to Reproduce

1. Download the "elastic-agent-7.10.0-amd64.deb" package.

2. SSH to the endpoint and place the agent package on /home/zeus location on Debian 9 Linux machine.

3. Hit the command to get the root/admin permission: sudo su root

4. Run the command: sudo dpkg -i elastic-agent-7.10.0-amd64.deb

5. Download elastic-agent.yml from Add agent ->Standalone mode on Agents tab in Kibana and add Kibana login username and password in outputs section of elastic-agent.yml (Modify ES_USERNAME and ES_PASSWORD in the outputs section of elastic-agent.yml to use your Elasticsearch credentials)
   elastic-agent_yml.zip

6. Copy elastic-agent.yml file to /home/zeus on Linux Debian 9 machine

7. Then execute: sudo cp /home/zeus/elastic-agent.yml /etc/elastic-agent/elastic-agent.yml

8. Run the following commands to run the standalone agent :-
   elastic-agent run

9. Execute the enroll command :-
   sudo elastic-agent enroll https://d9dc24b9e27749e8af99cb8d590ca97f.europe-west1.gcp.cloud.es.io:9243 Y1RKaHJIVUJHcXBIMWZsU1dLTEI6cEtfakhXVTJScUctUmJhUENiRFlZQQ==

10. Execute the below command to enable the agent :-
    systemctl enable elastic-agent

and observe that error is displayed in putty :-

Failed to reload daemon: The name org.freedesktop.PolicyKit1 was not provided by any .service files
update-rc.d: error: no runlevel symlinks to modify, aborting!

11. Execute the below command to start the agent :-
    systemctl start elastic-agent

and observe that following error is displayed in putty but agent comes in Online status and activity logs are displayed :-

Failed to start elastic-agent.service: The name org.freedesktop.PolicyKit1 was not provided by any .service files
See system logs and 'systemctl status elastic-agent.service' for details.

12. Run the command 'sudo reboot' and observe that agent goes to Offline status.

Test data
N/A

Impacted Test case id
https://elastic.testrail.io/index.php?/cases/view/34373

Actual Result
Agent goes to Offline status on reboot of Linux deb stand-alone agent enroll to Fleet

Expected Result
Agent should remain in Online status on reboot of Linux deb stand-alone agent enroll to Fleet

What's working

• Issue is not occurring on stand-alone agent enroll to Fleet with Linux rpm

What's not working

• N/A

Screenshot

1. Errors in putty on enabling and starting the agent:
   

2. Agent in Online status with activity logs on executing agent start command(before reboot):
   

3. Agent in Offline status after reboot:
   

4. Linux Debian 9 machine VSphere Template:
   

Logs
N/A