From 5a94449b77d6b52c99dd5581fde44b73b1d34f85 Mon Sep 17 00:00:00 2001 From: Dan Sneddon Date: Wed, 13 Sep 2017 17:53:36 -0600 Subject: Fix upgrades that use Management network Upgrades from older versions using Management network fail. This patch enables the management network even though it is not enabled in any of the role definitions. This will allow upgrades to complete using existing network environment files, without requiring operators to switch to the new method for defining which networks are attached to roles. Eventually these older environment files will be removed. Change-Id: Iadd12a559f0ad6918958a1355f189187fd327363 Closes-bug: 1717123 (cherry picked from commit 5b9fbc2b2bfa00de2fe0f437f21e05e3fc09a53d) --- network_data.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'network_data.yaml') diff --git a/network_data.yaml b/network_data.yaml index fed11576..bce82cb2 100644 --- a/network_data.yaml +++ b/network_data.yaml @@ -81,8 +81,9 @@ ipv6_subnet: 'fd00:fd00:fd00:5000::/64' ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:5000::10', 'end': 'fd00:fd00:fd00:5000:ffff:ffff:ffff:fffe'}] - name: Management - # Management network is disabled by default - enabled: false + # Management network is enabled by default for backwards-compatibility, but + # is not included in any roles by default. Add to role definitions to use. + enabled: true vip: false # Management network does not use VIPs name_lower: management ip_subnet: '10.0.1.0/24' -- cgit 1.2.3-korg