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] [Comment Edited] (BROOKLYN-450) Brooklyn deployments fail on Azure ARM when VM hostname is changed
Date Mon, 13 Mar 2017 21:41:41 GMT

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

Yavor Yanchev edited comment on BROOKLYN-450 at 3/13/17 9:41 PM:
-----------------------------------------------------------------

You have to change the default Azure linux configuration to resolve the problem. It can be
achieved via edit of the default configuration file available on the provisioned VM as /etc/waagent.conf

Changing of the default value of Provisioning.MonitorHostName from

{code}
Provisioning.MonitorHostName=y
{code}

to 

{code}
Provisioning.MonitorHostName=n
{code}

Changing of the default value from Y (yes) to N (no) will prevent the agent from detecting
the hostname change and initiating the network disruption. The reported behavior 
{code}
Provisioning.MonitorHostName:
Type: Boolean
Default: y

If set, waagent will monitor the Linux virtual machine for hostname changes (as returned by
the "hostname" command) and automatically update the networking configuration in the image
to reflect the change. In order to push the name change to the DNS servers, networking will
be restarted in the virtual machine. This will result in brief loss of Internet connectivity.
{code}

is described in the Azure docs - https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-linux-agent-user-guide


was (Author: yanchev):
You have to change the default Azure linux configuration to resolve the problem. It can be
achieved via edit of the default configuration file available on the provisioned VM as /etc/waagent.conf

Changing of the default value of Provisioning.MonitorHostName from

{code}
Provisioning.MonitorHostName=y
{code}

to 

{code}
Provisioning.MonitorHostName=n
{code}

This change will prevent the agent from detecting the hostname change and initiating the network
disruption. The reported behavior 
{code}
Provisioning.MonitorHostName:
Type: Boolean
Default: y

If set, waagent will monitor the Linux virtual machine for hostname changes (as returned by
the "hostname" command) and automatically update the networking configuration in the image
to reflect the change. In order to push the name change to the DNS servers, networking will
be restarted in the virtual machine. This will result in brief loss of Internet connectivity.
{code}

is described in the Azure docs - https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-linux-agent-user-guide

> 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