CLOUD_NETCONFIG_MANAGE in a HA Cluster
This document (7023633) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise High Availability Extension 15
SUSE Linux Enterprise High Availability Extension 12
SUSE Linux Enterprise High Availability Extension 12
Situation
Check the installed cloud-netconfig-azure package version by running zypper info cloud-netconfig-azure.
If the version is 1.3 or higher, it is no longer necessary to suppress the management of network interfaces by the cloud network plugin. If the version is lower than 1.3, we suggest to update package cloud-netconfig-azure to the latest available version.
-
For cloud-netconfig-azure package version lower than 1.3:
In a HA Cluster in a Cloud Enviroment a configured IP Address sometimes disappears resulting in a restart or sometimes even a resource migration - see Resolution section.
If the version is 1.3 or higher, it is no longer necessary to suppress the management of network interfaces by the cloud network plugin. If the version is lower than 1.3, we suggest to update package cloud-netconfig-azure to the latest available version.
-
For cloud-netconfig-azure package version lower than 1.3:
In a HA Cluster in a Cloud Enviroment a configured IP Address sometimes disappears resulting in a restart or sometimes even a resource migration - see Resolution section.
Resolution
In the configuration file of the network interface,
/etc/sysconfig/network/ifcfg-eth0
modify the option
CLOUD_NETCONFIG_MANAGE="yes"
is set. This has to be set to
CLOUD_NETCONFIG_MANAGE="no"
Cause
When enabled, the CLOUD_NETCONFIG_MANAGE parameter, a feature of the Azure cloud netconfig plugin, regularly probes the Azure Instance Metadata Service (IMDS) on the platform to determine the IP addresses assigned to an interface. IP addresses exposed via this API are automatically added to the respective interface by the plugin, and when removed from the platform, they are automatically removed from the interface. This is a good and desirable behavior normally.
In an HA cluster in Azure, a client connects to a clustered service via an IP address that is dynamically set by a cluster IP resource. This "floating" cluster IP is configured on the platform via an Azure Load Balancer and not assigned directly to an interface.
As such the two concepts conflict with each other.
In cloud-netconfig v1.2 and earlier, it is recommended to set the parameter to "no" to ensure that the IP won't be touched.
The cloud-netconfig v1.3 update was designed to resolve this conflict.
In an HA cluster in Azure, a client connects to a clustered service via an IP address that is dynamically set by a cluster IP resource. This "floating" cluster IP is configured on the platform via an Azure Load Balancer and not assigned directly to an interface.
As such the two concepts conflict with each other.
In cloud-netconfig v1.2 and earlier, it is recommended to set the parameter to "no" to ensure that the IP won't be touched.
The cloud-netconfig v1.3 update was designed to resolve this conflict.
Additional Information
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7023633
- Creation Date: 11-Jan-2019
- Modified Date:12-Sep-2022
-
- SUSE Linux Enterprise High Availability Extension
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
