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

Bharat Kumar updated CLOUDSTACK-9035:
-------------------------------------
    Description: 
we send the save password command to both the VRs in a rvr enabled network, But 
the password gets saved only in the master VR. This happens because the 
password server is not running in the backup. 

Because of this if someone resets the password of a VM and starts it when the 
backup becomes master. Then the password of the user VM will not change, 
because the save password command was not successful.

  was:
we send the save password command to both the VRs in a rvr enabled network, But 
the password gets saved only in the master VR. This happens because the 
password server is not running in the backup. 

Because of this if someone resets the password of a VM and starts it when the 
backup becomes master. Then the password of the user VM will not change, 
because the save password was not successful.


> Password file is stored only with Master when we Reset Password on the VM.
> --------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9035
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9035
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Virtual Router
>    Affects Versions: 4.6.0
>            Reporter: Bharat Kumar
>            Priority: Blocker
>             Fix For: 4.6.0
>
>
> we send the save password command to both the VRs in a rvr enabled network, 
> But the password gets saved only in the master VR. This happens because the 
> password server is not running in the backup. 
> Because of this if someone resets the password of a VM and starts it when the 
> backup becomes master. Then the password of the user VM will not change, 
> because the save password command was not successful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to