mco triggered automatic deployments. Effected production/Staging Servers.

[pradeep reddy]

Hi All,

We are using a ruby script, which uses mcollective API for initiating the puppet run on multiple servers based on the group and track its status. 

It used to do the rolling deployment or in other words initiate puppet agent on the servers.

We are using from three years same setup.  But observed that, today we have mco automatic trigger issue.  It effected, lot of servers.

Could someone please let us know, or guide us in finding the issue.

Puppet Server Details:-

------------

 puppet -V  ----> 3.4.2

 mcollective-service-client-3.1.2-1.noarch

 mcollective-client-2.4.0-1.el6.noarch

 mcollective-nettest-common-3.0.3-1.noarch

 mcollective-common-2.4.0-1.el6.noarch

 mcollective-iptables-client-3.0.1-1.noarch

 mcollective-puppet-agent-1.6.0-1.noarch

 mcollective-filemgr-client-1.0.1-1.noarch

 mcollective-puppet-client-1.6.0-1.noarch

 mcollective-package-client-4.2.1-1.el6.noarch

 mcollective-iptables-common-3.0.1-1.noarch

 mcollective-puppet-common-1.6.0-1.noarch

 mcollective-filemgr-common-1.0.1-1.noarch

 mcollective-iptables-agent-3.0.1-1.noarch

 mcollective-package-agent-4.2.1-1.el6.noarch

 mcollective-nettest-client-3.0.3-1.noarch

 mcollective-nettest-agent-3.0.3-1.noarch

 mcollective-package-common-4.2.1-1.el6.noarch

 mcollective-service-common-3.1.2-1.noarch

 mcollective-filemgr-agent-1.0.1-1.noarch

 mcollective-2.4.0-1.el6.noarch

 Puppet agent Details:-

 --------------

 mcollective-puppet-common-1.9.3-1.el6.noarch

 mcollective-puppet-agent-1.9.3-1.el6.noarch

 puppet-3.7.4-1.el6.noarch

Thanks and Regards,

Pradeep.