Bug 1425096

> Additional info:
> This is fixed by
> https://trunk.rdoproject.org/centos7/current/puppet-pacemaker-0.5.0-0.
> 20170214145103.b135ebb.el7.centos.noarch.rpm

This build is master not ocata.  puppet-pacemaker appears branchless, so we need to get the pin updated in RDO in order to get this downstream.

(In reply to Mike Burns from comment #2)
> > Additional info:
> > This is fixed by
> > https://trunk.rdoproject.org/centos7/current/puppet-pacemaker-0.5.0-0.
> > 20170214145103.b135ebb.el7.centos.noarch.rpm
> 
> This build is master not ocata.  puppet-pacemaker appears branchless, so we
> need to get the pin updated in RDO in order to get this downstream.

Hi Mike, I'll be happy to help here although I am not entirely sure what "updating the pin in RDO" entails. Do I just need to ping Haikel/Alan and they will know?

(In reply to Michele Baldessari from comment #3)
> (In reply to Mike Burns from comment #2)
> > > Additional info:
> > > This is fixed by
> > > https://trunk.rdoproject.org/centos7/current/puppet-pacemaker-0.5.0-0.
> > > 20170214145103.b135ebb.el7.centos.noarch.rpm
> > 
> > This build is master not ocata.  puppet-pacemaker appears branchless, so we
> > need to get the pin updated in RDO in order to get this downstream.
> 
> Hi Mike, I'll be happy to help here although I am not entirely sure what
> "updating the pin in RDO" entails. Do I just need to ping Haikel/Alan and
> they will know?

Yes, Alan/Haikel can help you out with this.

Background on puppet pins is in commit msg from amoralej in https://review.rdoproject.org/r/4673
tl;dr we pin at RC  time last-known-good puppet modules which do not do releases

To update it, look for - project: puppet-pacemaker in rdoinfo and update source-branch under ocata
as done by Haikel for this issue in https://review.rdoproject.org/r/5568

Mike, I think we should be good here now?
https://trunk.rdoproject.org/centos7-ocata/current/puppet-pacemaker-0.5.0-0.20170302152311.fe4d448.el7.centos.noarch.rpm

bump... still hitting this on latest OSP11 puddle (the workaround that works for me today is to install puppet-pacemaker from rdo repos)


[root@overcloud-controller-0 ~]# rpm -qa | grep puppet-pacemaker
puppet-pacemaker-0.4.0-1.el7ost.noarch


        2017-03-08 14:14:50Z [overcloud-AllNodesDeploySteps-5ynyyqxffekt.AllNodesPostUpgradeSteps.ControllerDeployment_Step1]: CREATE_FAILED  Error: resources.ControllerDeployment_Step1.resources[1]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1
        2017-03-08 14:14:51Z [overcloud-AllNodesDeploySteps-5ynyyqxffekt.AllNodesPostUpgradeSteps]: CREATE_FAILED  Resource CREATE failed: Error: resources.ControllerDeployment_Step1.resources[1]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1
        2017-03-08 14:14:51Z [overcloud-AllNodesDeploySteps-5ynyyqxffekt.AllNodesPostUpgradeSteps]: CREATE_FAILED  Error: resources.AllNodesPostUpgradeSteps.resources.ControllerDeployment_Step1.resources[1]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1
        2017-03-08 14:14:51Z [overcloud-AllNodesDeploySteps-5ynyyqxffekt]: UPDATE_FAILED  Error: resources.AllNodesPostUpgradeSteps.resources.ControllerDeployment_Step1.resources[1]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1
        2017-03-08 14:14:52Z [AllNodesDeploySteps]: UPDATE_FAILED  resources.AllNodesDeploySteps: Error: resources.AllNodesPostUpgradeSteps.resources.ControllerDeployment_Step1.resources[1]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1
        2017-03-08 14:14:52Z [overcloud]: UPDATE_FAILED  resources.AllNodesDeploySteps: Error: resources.AllNodesPostUpgradeSteps.resources.ControllerDeployment_Step1.resources[1]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1

         Stack overcloud UPDATE_FAILED 

        Heat Stack update failed.

        Mar 08 14:14:47 overcloud-controller-0.localdomain os-collect-config[262395]: t::Integer. There is further documentation for validate_legacy function in the README. at [\"/var/lib/heat-config/heat-config-puppet/2faf3c95-eb15-42ef-a747-a25b016b8e31.pp\", 72]:[\"/etc/puppet/modules/tripleo/manifests/profile/pacemaker/rabbitmq.pp\", 62]\n   (at /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')\u001b[0m\n\u001b[1;33mWarning: Unknown variable: 'haproxy_stats_bind_certificate'. at /etc/puppet/modules/tripleo/manifests/haproxy.pp:769:6\u001b[0m\n\u001b[1;33mWarning: This method is deprecated, please use match expressions with Stdlib::Compat::String instead. They are described at https://docs.puppet.com/puppet/latest/reference/lang_data_type.html#match-expressions. at [\"/var/lib/heat-config/heat-config-puppet/2faf3c95-eb15-42ef-a747-a25b016b8e31.pp\", 77]:[\"/etc/puppet/modules/tripleo/manifests/profile/base/memcached.pp\", 30]\n   (at /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')\u001b[0m\n\u001b[1;31mError: Evaluation Error: Error while evaluating a Resource Statement, Class[Pacemaker::Stonith]: has no parameter named 'tries' at /etc/puppet/modules/tripleo/manifests/profile/base/pacemaker.pp:105:5 on node overcloud-controller-0.localdomain\u001b[0m\n", "deploy_status_code": 1}

Mike, I think we should "just" pull this in a new puddle, right?

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1245