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

ASF subversion and git services commented on CLOUDSTACK-2180:
-------------------------------------------------------------

Commit 35e50761562fc558ec7e272cc7dbd1cff564d356 in branch 
refs/heads/4.2-forward from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=35e5076 ]

CLOUDSTACK-2180: UI > Instances ? Reboot VM action > if the template from which 
vm is created is password-enabled, pop up "Password has been reset to xxxxxxx" 
dialog after action is complete.

                
> CLONE - restoreVirtualMachine returns no password
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-2180
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2180
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.2.0
>         Environment: hypervisor: Ubuntu 12.04 (64-bit)
> CloudStack 4.0.1
> Guest OS: Ubuntu 10.04 (64-bit)
>            Reporter: Harikrishna Patnala
>            Assignee: Harikrishna Patnala
>
> We just had a test on restoreVirtualMachine. no password is returned.
> To reproduce:
> (1) run
> command=restoreVirtualMachine&response=json&virtualmachineid=1a53a308-c870-452a-9eff-23975919286b
>  
> (2) query 
> command=queryAsyncJobResult&response=json&jobid=77c60ca2-8b14-4a14-9449-7855c5e67fff
> passwordenabled is true, but no password is returned. I can not log in the 
> virtual machine using the old password.
> (3) workaround 
> command=resetPasswordForVirtualMachine&id=1a53a308-c870-452a-9eff-23975919286b
>  
> will restart the virtual machine and set a new password. I can log in the 
> virtual machine using this password
> Hope the guys working on CLOUDSTACK-667 (VM's base image update facility) can 
> consider this issue.

--
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