brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yavor Yanchev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-450) Brooklyn deployments fail on Azure ARM when VM hostname is changed
Date Mon, 13 Mar 2017 21:31:41 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922980#comment-15922980
] 

Yavor Yanchev commented on BROOKLYN-450:
----------------------------------------

It tuns out that the problem is caused by the running Azure linux agent on the provisioned
machine. Amabri blueprint will change the VM's hostname as part of the deployment process.
Azure linux agent will detect that change (as instructed by default) and will try to update
the Azure hostname configuration and initiate DHCP change. The change will restart the VM
network scripts as well. VM gets changed network configuration with interruptions which is
causing some package managers to fail when they are trying to resolve the remote software
repositories' web addresses to install the software packages.

> Brooklyn deployments fail on Azure ARM when VM hostname is changed
> ------------------------------------------------------------------
>
>                 Key: BROOKLYN-450
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-450
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.11.0
>            Reporter: Yavor Yanchev
>
> When Brooklyn 0.11.0-SNAPSHOT is used to deploy blueprints on Azure ARM it might express
issues during service installation



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message