Stop no-opping PackageUpdate on upgrade
authorJiri Stransky <jistr@redhat.com>
Fri, 1 Jul 2016 12:25:59 +0000 (14:25 +0200)
committerJiri Stransky <jistr@redhat.com>
Fri, 1 Jul 2016 12:25:59 +0000 (14:25 +0200)
After we fixed bug #1567384 and bug #1567385, we no longer need to no-op
the PakageUpdate resource on upgrades. I removed the no-op in change
Ie14ddbff15e7ed21aaa3fcdacf36e0040f912382 from
major-upgrade-pacemaker-converge.yaml but didn't recall we had the no-op
in major-upgrade-pacemaker{,-init}.yaml too.

Change-Id: I24b913c790eae79e3b207729e0b22378075fb282

environments/major-upgrade-pacemaker-init.yaml
environments/major-upgrade-pacemaker.yaml

index fbad040..d97f8fc 100644 (file)
@@ -3,7 +3,6 @@ parameter_defaults:
 
 resource_registry:
   OS::TripleO::Tasks::UpdateWorkflow: ../extraconfig/tasks/major_upgrade_pacemaker_init.yaml
-  OS::TripleO::Tasks::PackageUpdate:  ../extraconfig/tasks/yum_update_noop.yaml
   OS::TripleO::ControllerPostDeployment: OS::Heat::None
   OS::TripleO::ComputePostDeployment: OS::Heat::None
   OS::TripleO::ObjectStoragePostDeployment: OS::Heat::None
index 763ca67..95f0966 100644 (file)
@@ -3,7 +3,6 @@ parameter_defaults:
 
 resource_registry:
   OS::TripleO::Tasks::UpdateWorkflow: ../extraconfig/tasks/major_upgrade_pacemaker.yaml
-  OS::TripleO::Tasks::PackageUpdate:  ../extraconfig/tasks/yum_update_noop.yaml
   OS::TripleO::ControllerPostDeployment: OS::Heat::None
   OS::TripleO::ComputePostDeployment: OS::Heat::None
   OS::TripleO::ObjectStoragePostDeployment: OS::Heat::None