[
https://issues.apache.org/jira/browse/CLOUDSTACK-9763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865524#comment-15865524
]
ASF GitHub Bot commented on CLOUDSTACK-9763:
--------------------------------------------
Github user serbaut commented on the issue:
https://github.com/apache/cloudstack/pull/1919
The VPC VR maintains metadata
(http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/virtual_machines/user-data.html)
as static files in /var/www/html/metadata. When a VR is destroyed and
recreated (by e.g. "restart with cleanup") this metadata is rebuilt by
createVmDataCommandForVMs(). public-keys is missing from that function so it
becomes empty after the rebuild and a request for latest/meta-data/public-keys
no longer returns the correct key.
This PR adds public-key to the rebuild.
> 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)
