The public key being removed from the VR is the correct behavior. The VR has a 
cache that stores the ssh key when you make the API call and once it has been 
requested is removed from the cache.

Travis

On Oct 11, 2013, at 4:31 AM, Stanislav Petrov <devilfighter1...@gmail.com> 
wrote:

> Hi all,
> 
> My Environment is: CS 4.1.1, KVM hypervisor
> 
> Here is the use case steps:
> 1. Create SSH keypair "keypairname" through the REST API.
> 2. Deploy VM with the created keypair from step 1.
> 3. On the VM, the url "http://<dhcpserverip>/latest/public-keys" returns
> the public key.
> 4. Update the running VM with userdata.
> 5. On the VM, the url "http://<dhcpserverip>/latest/public-keys" returns
> nothing and the user data url "http://<dhcpserverip>/latest/user-data"
> returns the user-data which was set in step 4.
> 
> Result: User data is set but public key is gone (cleaned).
> 
> When I update user data on a stopped VM, both SSH public key and user data
> are available.
> 
> Is this behavior expected or is this some kind of an issue ?
> 
> -- 
> Best regards,
> Stanislav Petrov

Reply via email to