[
https://issues.apache.org/jira/browse/CLOUDSTACK-9763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865943#comment-15865943
]
ASF GitHub Bot commented on CLOUDSTACK-9763:
--------------------------------------------
Github user rafaelweingartner commented on the issue:
https://github.com/apache/cloudstack/pull/1919
Thanks for the explanation @serbaut. That is exactly why I asked; so, it is
not a reboot/restart per se. It is a re-deploy; the old virtual machine is
destroyed and a new one is deployed (or maybe a reset of the VHD of the VM). By
VM here I mean VR (which at the end of the day is a VM).
@serbaut, could you add these explanations on the PR description and Jira
ticket (https://issues.apache.org/jira/browse/CLOUDSTACK-9763)? At least for
me, this was not clear.
Thanks for the fix ;)
Code LGTM
> 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)
