mcollective service getting restarted after agent upgrade using "puppet_agent" module

This case is raised based on the customer ticket "https://puppetlabs.zendesk.com/agent/tickets/34920". When Puppet agent on Solaris 10 node upgraded using module "pppet_agent", it is starting "mcollective" service. "mcollective" is disabled in this PE 2018.1.8.

Adding an additional condition to check the current mcollective status and assign the $service_names in "https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/manifests/params.pp#L14" will resolve the issue.
=======
bash-4.2# uname -a
SunOS -f 5.10 Generic_147148-26 i86pc i386 i86pc
bash-4.2# cat /etc/release
Oracle Solaris 10 1/13 s10x_u11wos_24a X86
Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.
Assembled 17 January 2013

bash-4.2# puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Loading facts
Info: Caching catalog for sd3juh5n8mohjio.delivery.puppetlabs.net
Info: Applying configuration version 'pe-201815-master-production-9f181eb4f67'
Notice: /Stage[main]/Puppet_agent::Prepare::Package/File[/opt/puppetlabs/packages/puppet-agent-5.5.8-1.i386.pkg.gz]/ensure: defined content as '

94115280bf9d11c40d32556ad283a8160c1535dc0a27173ad38cd09b9153d921'
Notice: /Stage[main]/Puppet_agent::Osfamily::Solaris/Exec[unzip puppet-agent-5.5.8-1.i386.pkg.gz]/returns: executed successfully
Notice: /Stage[main]/Puppet_agent::Install/File[/tmp/solaris_install.sh]/ensure: defined content as '

f49acfaac67adf5b1911fc030b7f0355'
Notice: /Stage[main]/Puppet_agent::Install/Exec[solaris_install script]/returns: executed successfully
Notice: Applied catalog in 3.39 seconds

bash-4.2# cat /tmp/solaris_install.sh
#!/bin/bash
...

Ensure services are running
start_service puppet
start_service mcollective
...