You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kiran Koneti (JIRA)" <ji...@apache.org> on 2013/12/19 13:15:07 UTC

[jira] [Closed] (CLOUDSTACK-5188) Password reset of vm on Xen and VMware does not work on first reboot

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Koneti closed CLOUDSTACK-5188.
------------------------------------


Verified this in the Xen and Vmware setup both are working fine in the latest 4.3 hence closing the defect.

> Password reset of vm on Xen and VMware does not work on first reboot
> --------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5188
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5188
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Test
>    Affects Versions: 4.2.1, 4.3.0
>         Environment: VMware and Xen
>            Reporter: Girish Shilamkar
>            Assignee: Jayapal Reddy
>            Priority: Blocker
>
> The issue was uncovered as test_vm_passwdenabled.py was consistently failing on Vmware and Xen. Note this issue is not seen on KVM.
> Procedure:
> 1. Create a vm
> 2. Enable password management. In vm do following:
> $ cd /etc/init.d
> $ wget http://people.apache.org/~tsp/cloud-set-guest-password
> $ chmod +x /etc/init.d/cloud-set-guest-password
> $ chkconfig --add cloud-set-guest-password
> 3. Stop vm
> 4. Create template from vm's volume
> 5. Delete vm
> 6. Create new vm from template created in step 4
> 7. Stop vm
> 8. Reset password
> 9. Start vm
> 10. Ssh to vm using password obtained in step 8
> The ssh to vm using new password will fail but ssh with old password works
> Now if vm is stopped and started again, the new password will work. Thus password is reset only on the second boot.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)