Updates:
Status: WontFix
Comment #6 on issue 990 by [email protected]: "gnt-cluster verify" not
using ssh-agent
https://code.google.com/p/ganeti/issues/detail?id=990
Hi!
I had a look at this, and I think what you are describing is actually
intended by design.
When initializing and adding cluster nodes, ganeti (tries to use) the
agent, because in order add a node, it would need some kind ssh connection
for the operations necessary to add the nodes. This could be the key loaded
in an agent or a key of the master node that is manually added to the new
node.
However, after adding nodes, Ganeti assumes that is has all keys etc. to
reach all nodes without having to rely on a user logged in and having a key
loaded in an agent. For example you could run 'gnt-cluster verify' in the
middle of the night with a cron job, you also don't necessarily have a key
loaded.
So, it is actually intended, that each node has an id_dsa file and removing
it makes Ganeti indeed unhappy.
I am sorry I am getting to this so late, I misread the bug at first.
I am closing this for now. Feel free to revive the discussion if you have
more points for your use case.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
