voxpupuli/puppet-corosync

Warning: Found multiple default providers for cs_primitive: crm, pcs; using crm

amfournda opened this issue · 1 comments

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 7.23.0
  • Ruby: 3.1.2p20 (2022-04-12 revision 4491bb740a)
  • Distribution: Debian 12 (bookworm)
  • Module version: v8.2.0

How to reproduce (e.g Puppet code you use)

I have a node definition in my r10k manifest that includes the corosync class and defines some primitives:

node 'server1.tld' {
     include ::corosync
     cs_property { 'stonith-enabled' :
          value   => 'false',
     }
     cs_property { 'no-quorum-policy' :
          value   => 'ignore',
     }
     cs_primitive { 'apache2_vip':
          primitive_class => 'ocf',
          primitive_type  => 'IPaddr2',
          provided_by     => 'heartbeat',
          parameters      => { 'ip' => ''172.16.251.10', 'cidr_netmask' => '24' },
          operations      => { 'monitor' => { 'interval' => '10s' } },
     }
}

And then I can put the basic data in Hiera

---
corosync::bind_address: 172.16.251.11
corosync::cluster_name: paradox
corosync::enable_secauth: false
corosync::quorum_members:
  - '172.16.251.11'
  - '172.16.251.12'
corosync::quorum_members_names:
  - 'server1'
  - 'server2'

What are you seeing

When I run puppet I get this warning:

# > puppet agent --test
Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Warning: Found multiple default providers for cs_property: crm, pcs; using crm
Warning: Found multiple default providers for cs_primitive: crm, pcs; using crm
Warning: Found multiple default providers for cs_clone: crm, pcs; using crm
Warning: Found multiple default providers for cs_colocation: crm, pcs; using crm
Info: Caching catalog for paradox-01.cts
Info: Applying configuration version '1699298723'
Notice: Applied catalog in 29.69 seconds

What behaviour did you expect instead

This doesn't appear to cause any problems. Running crm status reports a happy cluster of my two servers and my resource works perfectly. It would be nice if I could suppress these warnings somehow as not to clutter my logging/monitoring. If this issue can be assigned a low priority, it should be.

In case it wasn't clear, this happens because both crm and pcs are installed on the host. Removing one makes the warning go away.