[
https://issues.apache.org/jira/browse/CLOUDSTACK-9763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864397#comment-15864397
]
ASF GitHub Bot commented on CLOUDSTACK-9763:
--------------------------------------------
Github user rafaelweingartner commented on the issue:
https://github.com/apache/cloudstack/pull/1919
@serbaut I would only like to make a few questions to see if I understood
the issue here, before evaluating the code any further.
When you first deploy the VM, the keys are delivered to the newly deployed
VM, right? The problem only happens on reboots?
Do we need to always keep sending the same access keys? Is not one time
enough? Of course, if the keys are changed, we should send them; but otherwise,
it feels that we should not need to keep sending them.
> vpc: can not ssh to instance after vpc restart
> ----------------------------------------------
>
> Key: CLOUDSTACK-9763
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9763
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router, VPC
> Affects Versions: 4.8.0
> Reporter: Joakim Sernbrant
>
> Restart with Cleanup of a VPC does not update the public-key metadata, it is
> explicitly set to null in
> https://github.com/apache/cloudstack/blob/master/server/src/com/cloud/network/router/CommandSetupHelper.java#L614
> Rebooting instances relying on metadata (e.g. coreos) will no longer have the
> correct public key configured.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
