[
https://issues.apache.org/jira/browse/BROOKLYN-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage updated BROOKLYN-483:
-------------------------------
Summary: Brooklyn cannot initiate first SSH connection on Azure-classic
(was: Brooklyn cannot initiate first SSH connection on Azure)
> Brooklyn cannot initiate first SSH connection on Azure-classic
> --------------------------------------------------------------
>
> Key: BROOKLYN-483
> URL: https://issues.apache.org/jira/browse/BROOKLYN-483
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.11.0
> Reporter: Thomas Bouron
>
> I'm trying to deploy a very simple blueprint
> {code}
> location: azure-sng-minimal
> services:
> - type: org.apache.brooklyn.entity.software.base.EmptySoftwareProcess
> {code}
> on a minimal Azure location:
> {code}
> brooklyn.catalog:
> id: azure-sng-minimal
> itemType: location
> name: "Azure Southeast Asia (SNG) Minimal"
> item:
> type: jclouds:azurecompute
> brooklyn.config:
> regionId: Southeast Asia
> identity: /Users/thomasbouron/.ssh/azure.p12
> credential: xxxxxxxx
> endpoint:
> https://management.core.windows.net/341751b0-f348-45ce-9498-xxxxxxxxxxxxxxxxxxxxx
> {code}
> Brooklyn is able to provisioned the VM but fails to initiate the first SSH
> connection:
> {code}
> 2017-04-19 10:38:23,702 INFO 334 o.a.b.r.r.ApplicationResource
> [qtp235840421-124] Launched from YAML: location: azure-sng-minimal
> - type: "elasticsearch-node-tests_19042017_103735:1.0.2-SNAPSHOT" ->
> BasicApplicationImpl{id=b6lgwpmnrj} (Task[start]@tfqRf4JU)
> 2017-04-19 10:38:23,858 INFO 129 o.a.b.e.s.b.l.MachineLifecycleEffectorTasks
> [ager-iWm4jv3o-17] Starting VanillaSoftwareProcessImpl{id=f7iv5s8u2x},
> obtaining a new location instance in JcloudsLocation[Azure Southeast Asia
> (SNG) Minimal:/amp/azure.p12@azkm52sknu] with ports [22, 9330, 9200]
> 2017-04-19 10:38:24,760 INFO 125 o.a.b.l.j.JcloudsLocation
> [ager-iWm4jv3o-17] Creating VM
> azurecompute:https://management.core.windows.net/341751b0-f348-45ce-9498-xxxxxxxxxxxxxxxxx@VanillaSoftwareProcessImpl{id=f7iv5s8u2x}
> in JcloudsLocation[Azure Southeast Asia (SNG)
> Minimal:/users/thomasbouron/.ssh/azure.p12@azkm52sknu]
> 2017-04-19 10:39:09,962 INFO 106 j.compute [user thread 0] Cloud Service
> (brooklyn-oonk80-root-elastic-b6lg-elasticsearchnod-f7iv-caa) created with
> operation id: 76008c93b18d74c797f17958fa336eb6
> 2017-04-19 10:39:36,713 INFO 106 j.compute [user thread 0] Deployment
> created with name: brooklyn-oonk80-root-elastic-b6lg-elasticsearchnod-f7iv-caa
> 2017-04-19 10:41:53,917 INFO 106 j.ssh [user thread 1] <<
> (jclouds:pw[cdfb4472683ad9b4f7e159935dbc439a]@40.71.103.245:22) error
> acquiring {hostAndPort=40.71.103.245:22, loginUser=jclouds, ssh=null,
> connectTimeout=60000, sessionTimeout=60000} (attempt 1 of 50): Exhausted
> available authentication methods
> 2017-04-19 10:41:56,108 INFO 106 j.ssh [user thread 1] <<
> (jclouds:pw[cdfb4472683ad9b4f7e159935dbc439a]@40.71.103.245:22) error
> acquiring {hostAndPort=40.71.103.245:22, loginUser=jclouds, ssh=null,
> connectTimeout=60000, sessionTimeout=60000} (attempt 2 of 50): Exhausted
> available authentication methods
> 2017-04-19 10:41:58,946 INFO 106 j.ssh [user thread 1] <<
> (jclouds:pw[cdfb4472683ad9b4f7e159935dbc439a]@40.71.103.245:22) error
> acquiring {hostAndPort=40.71.103.245:22, loginUser=jclouds, ssh=null,
> connectTimeout=60000, sessionTimeout=60000} (attempt 3 of 50): Exhausted
> available authentication methods
> ...
> {code}
> Looks like the default {{loginUser}} picked by jClouds is wrong. I know I can
> specify my own {{loginUser}} but I would expected jClouds to do this for me
> on basic locations
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
