Make UpgradeLevelNovaCompute parameters consistent
authorBen Nemec <bnemec@redhat.com>
Fri, 14 Jul 2017 20:36:56 +0000 (15:36 -0500)
committerBen Nemec <bnemec@redhat.com>
Wed, 2 Aug 2017 21:20:12 +0000 (16:20 -0500)
There is logic in nova-base.yaml that depends on the default for
this parameter being '', and the nova-compute service only needs it
set to auto during upgrade.  That will be done by [1] anyway, so it
doesn't matter what the default is.  It's also not clear to me that
the nova-compute task is even needed now that we're post-Ocata, but
that's not a change I feel comfortable making.

1: https://github.com/openstack/tripleo-heat-templates/blob/master/environments/major-upgrade-composable-steps.yaml

Change-Id: Iccfcb5b68e406db1b942375803cfedbb929b4307
Partial-Bug: 1700664

puppet/services/nova-compute.yaml
puppet/services/nova-conductor.yaml
tools/yaml-validate.py

index a12bfd0..6e1f3f5 100644 (file)
@@ -97,7 +97,7 @@ parameters:
   UpgradeLevelNovaCompute:
     type: string
     description: Nova Compute upgrade level
-    default: auto
+    default: ''
   MigrationSshKey:
     type: json
     description: >
index a6638be..5abad45 100644 (file)
@@ -45,7 +45,7 @@ parameters:
   UpgradeLevelNovaCompute:
     type: string
     description: Nova Compute upgrade level
-    default: auto
+    default: ''
 
 conditions:
   nova_workers_zero: {equals : [{get_param: NovaWorkers}, 0]}
index 3504620..a096d69 100755 (executable)
@@ -75,7 +75,6 @@ PARAMETER_DEFINITION_EXCLUSIONS = {'ManagementNetCidr': ['default'],
                                    'NeutronBigswitchLLDPEnabled': ['default'],
                                    'NeutronWorkers': ['description'],
                                    'ServerMetadata': ['description'],
-                                   'UpgradeLevelNovaCompute': ['default'],
                                    'server': ['description'],
                                    'servers': ['description'],
                                    'ExtraConfig': ['description'],