[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459651#comment-13459651
 ] 

Marcus Sorensen commented on CLOUDSTACK-131:
--------------------------------------------

Ok, I think the patch still needs to be applied to 4.0 though. For example I am 
seeing this right now on one of my agents, even though the keys are correct and 
working. If I were to do something that required a key change it could break:

2012-09-19 17:58:56,165 DEBUG [cloud.agent.Agent] (agentRequest-Handler-5:null) 
Processing command: com.cloud.agent.api.ModifySshKeysCommand
2012-09-19 17:58:56,165 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) Failed to create file: java.io.IOException: 
Permission denied
2012-09-19 17:58:56,166 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) Failed to create file: java.io.IOException: 
Permission denied

Yours definitely seems to be a key issue, either the ssvm isn't getting the 
updated authorized_keys, or its getting the wrong one somehow, or your host 
isn't getting a valid id_rsa.cloud. If you could troubleshoot as I mentioned by 
looking at the ssvm's authorized_keys that may give some clues. You can also 
set the agent to debug via /etc/cloud/agent/log4j-cloud.xml. You can run 
"ssh-keygen -y -f /root/.ssh/id_rsa.cloud" and that should spit out a public 
key identical to what should be in the ssvm's /root/.ssh/authorized_keys

                
> Templates other than SystemVM template are not getting downloaded on Rhel 6.3 
> ASF 4.0 setup with KVM host
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-131
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-131
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Management Server, Template
>    Affects Versions: pre-4.0.0
>         Environment: MS OS : Rhel 6.3
> Hypervisor : KVM
> BUILD : [Git Revision: 54f9af1695bc359b02e9fc906b3b335cc0bfec41
> Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
>            Reporter: Abhinav Roy
>            Assignee: edison su
>             Fix For: pre-4.0.0
>
>         Attachments: management-server.log
>
>
> Description :
> ======================
> Templates other than the systemvm template are not getting downloaded after 
> deploying a Basic/Advanced zone CS setup with KVM hypervisor.
> Steps :
> ======================
> Deploy a CS setup with KVM hypervisor.
> Expected behaviour :
> ======================
> Zone should be successfully deployed, system VMS should be created and the 
> default template should be deployed.
> Observed behaviour :
> ======================
> 1. Zone deployment is successful.
> 2. system-vms get created successfully.
> 3. But the problem is that there is no sign of deployment of any other 
> template (nothing seen in logs too), even if I try to manually register and 
> deploy a template it doesn't happen. 
> 4. Restarting system vm or management server doesn't change the behaviour.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to