cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9763) vpc: can not ssh to instance after vpc restart
Date Sat, 19 Aug 2017 19:00:03 GMT


ASF subversion and git services commented on CLOUDSTACK-9763:

Commit ea52a1312f2345dc2cdcbff31e326b7202453b42 in cloudstack's branch refs/heads/master from
[;h=ea52a13 ]

CLOUDSTACK-9763: set ssh public key when creating vm data (#1919)

> vpc: can not ssh to instance after vpc restart
> ----------------------------------------------
>                 Key: CLOUDSTACK-9763
>                 URL:
>             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 
> Rebooting instances relying on metadata (e.g. coreos) will no longer have the correct
public key configured.
> Added explanation:
> The VPC VR maintains metadata (
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 message was sent by Atlassian JIRA

View raw message