cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9727) Password reset discrepancy in RVR when one of the Router is not in Running state.
Date Mon, 13 Mar 2017 07:23:04 GMT


ASF GitHub Bot commented on CLOUDSTACK-9727:

Github user ustcweizhou commented on the issue:
    @bvbharatk Yes, you might know only the vm has sshkey attached will have the password
in vm details. If the vm does not have ssh keypair, then the vm password will not saved into
    Actually the vm password should be synced between master and backup. Saving to only one
of them or saving to both of them are not working fine.
    for example, if we save password in master, but not save it in backup. Once the master
is down, then vm cannot get password from backup vr.
    another example is, if we save password on both of master and backup, if vm get the password
from master and reset it, once the master is down (or master->backup switch) and we reboot
vm later, the vm will get the old password from backup again.

> Password reset discrepancy in RVR when one of the Router is not in Running state.
> ---------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-9727
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.9.0
>            Reporter: Bharat Kumar
>            Assignee: Bharat Kumar
>             Fix For:
> - Deploy an instance and place " cloud-set-guest-password " script in the /etc/init.d
location and provide the executable permission.
> - Create a template from the above VM.
> - Create a new network offering with RVR enabled.
> - Deploy a new VM from the above created template and select the above RVR offering.
> - Ensure that the password script is sucessfuly running.
> - Put the backup router in stopped state and ensure only master is running.
> - Now stop the VM and and Reset the password.
> - DO not start the VM , Now Stop the current Master and start the Back up.
> - Now the Back Up would be the Master. Now start the VM.
> Observations:
> - The password is saved onto only Master which is in stopped state now or either in backup
if we start it.
> - The current Master which was back up earlier do not have the new password. Hence user
cannot now login with the new password.
> - In this scenario there is disperancy in the password stored on both the RVR's.
> The only way to sync both the passwords now is , ensure both the RVR are running and
reset the password on VM. 

This message was sent by Atlassian JIRA

View raw message