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)
commit7f84409a6a21ce09042d4923236d2b05251af3af
treee1d93191b7380a5ffe66833410a346f888697a26
parentc05e72cd720b16383f5e4be8b774270f8fce6ca5
Make UpgradeLevelNovaCompute parameters consistent

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