[
https://issues.apache.org/jira/browse/DLAB-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-511:
-------------------------------
Sprint: (was: Apache DLab release 2.3)
> [GCP]: Instance connection is unsuccessful via GCP console due to failed to
> read key
> ------------------------------------------------------------------------------------
>
> Key: DLAB-511
> URL: https://issues.apache.org/jira/browse/DLAB-511
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Old
> Reporter: Vira Vitanska
> Assignee: Demyan Mysakovets
> Priority: Major
> Labels: Debian, DevOps, GCP
> Fix For: v.2.2, v.2.3
>
> Attachments: Connection.PNG
>
>
> *Preconditions:*
> # Edge is created
> # GCP console is open
>
> *Steps to reproduce:*
> # Click SSH drop down list related SSN or Edge
> # Choose 'open in browser window using provided private SSH key'
> # Choose your key.pem
>
> *Actual result:*
> 1. Connection is not successful
> 2. Error message appears 'Select a private ECDSA or RSA key file to sign into
> the VM or connect with a generated SSH key.'
>
> *Expected result:*
> 1. Connection is successful
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
