Description
In both the KVM and LXC node installation documentation; users are prompted to use the integrated SSH authentication agent service rather than distributing private keys.

However, in 4c Validate Connections, the command examples given will fail as the agent is not used nor forwarded in the hop to the nodes.

Current Content
https://docs.opennebula.io/7.2/software/installation_process/cluster_installation/kvm_node_installation/#c-validate-connections

https://docs.opennebula.io/7.2/software/installation_process/cluster_installation/lxc_node_installation/#c-validate-connections

Expected Content
Either:

• Recommend i.e. SSH_AUTH_SOCK=/var/run/one/ssh-agent.sock ssh -A <node1>
• Recommend beginning with export SSH_AUTH_SOCK=/var/run/one/ssh-agent.sock, then add -A to commands
• Instead of updating docs, update oneadmin profile to load the agent + update SSH config to agent forward by default

Affected doc version/s
7.2
7.0
6.10
(all since 5.12)

(Optional) Additional details
Previously reported:
https://forum.opennebula.io/t/is-the-opennbula-ssh-agent-supposed-to-work-without-any-extra-setup/10685/3
OpenNebula/minione#80