[
https://issues.apache.org/jira/browse/CLOUDSTACK-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000258#comment-15000258
]
ASF GitHub Bot commented on CLOUDSTACK-5822:
--------------------------------------------
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1044#issuecomment-155740283
Good point as well with the "unexpected". I definitely see where Wei is
coming from, but I think it could be misleading. Perhaps a better way to do
this is mark the ACS key and only reset that one. i.e.
When we add the key append a "# added by Cloudstack" and when we issue a
reset, just delete that one.
Am I overcomplicating this? I might be, especially as these scripts are
being slowly phased out.
> ssh keypairs are removed after rebooting vm
> -------------------------------------------
>
> Key: CLOUDSTACK-5822
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5822
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.3.0
> Reporter: Wei Zhou
> Assignee: Wei Zhou
>
> For a ssh keypair-enabled vm, the keys in /root/.ssh/authorized_keys will be
> reset after rebooting the vm. Only the keypair specified in cloudstack will
> be added. We should keep the keypairs added by users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
