On 08/28/2012 09:02 PM, Marcus Sorensen wrote:
Thanks. I've submitted a patch for the aforementioned permissions
issue. I'm still curious as to how the keys get on the systemvm if the
injectkeys only changes the iso on the management server, but that's
not a big deal.
The SSH key gets
On 08/28/2012 12:18 AM, Marcus Sorensen wrote:
Yes, thanks, this helps a lot.
Should cloud-agent write .ssh/id_rsa.cloud on every startup if
necessary? Or perhaps just on joining the cluster?
It's almost the same. When the Agent itself starts (joins the cluster
again) it receives the key
Thanks. I've submitted a patch for the aforementioned permissions
issue. I'm still curious as to how the keys get on the systemvm if the
injectkeys only changes the iso on the management server, but that's
not a big deal.
On Tue, Aug 28, 2012 at 8:51 AM, Wido den Hollander w...@widodh.nl wrote:
Guys,
In development/testing, I occasionally run into issues with the ssh
keys on the system VMs. Today specifically, I've been trying to hunt
down issues most of the day and still only have a hunch about the
process. Most of what I'm finding are the default authorized_keys
(anthony@mobl-ant),
On 08/27/2012 11:26 PM, Marcus Sorensen wrote:
Guys,
In development/testing, I occasionally run into issues with the ssh
keys on the system VMs. Today specifically, I've been trying to hunt
down issues most of the day and still only have a hunch about the
process. Most of what I'm finding
Yes, thanks, this helps a lot.
Should cloud-agent write .ssh/id_rsa.cloud on every startup if
necessary? Or perhaps just on joining the cluster?
I only see one reference to injectkeys.sh, and it's called via
injectSshKeysIntoSystemVmIsoPatch as injectkeys.sh public key
private key systemvm.iso
ok, so one little part I found, the reason why my /root/.ssh files
weren't being updated, is that I was getting:
2012-08-27 16:35:40,227 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-4:null) Processing command:
com.cloud.agent.api.ModifySshKeysCommand
2012-08-27 16:35:40,228 DEBUG
