You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: 5.5.5
Ruby: 2.4.4
Distribution: RedHat Enterprise Linux 7.5
Module version: 6.0.1
Cluster package versions
pcs: 0.9.162
corosync: 2.4.3
pacemaker: 1.1.18
How to reproduce (e.g Puppet code you use)
The example below details the initialization of a the SAPInstance resource for a particular configuration that uses the master/slave 2-node topology. This code functions normally on the first apply, however, subsequent applies fail because the cs_primitive pcs provider generates a malformed command.
Affected Puppet, Ruby, OS and module versions/distributions
Cluster package versions
How to reproduce (e.g Puppet code you use)
The example below details the initialization of a the SAPInstance resource for a particular configuration that uses the master/slave 2-node topology. This code functions normally on the first apply, however, subsequent applies fail because the cs_primitive pcs provider generates a malformed command.
What are you seeing
This is the error generated on a subsequent apply by the pcs provider.
What behaviour did you expect instead
I expect it not to error. Based on my understanding of the command, the updated should include the name of the master resource, not the base.
The following command works without error:
Any additional information you'd like to impart
I believe simply removing the
(@property_hash[:name]).to_s
from the end of the array in the line below would correct this issue.puppet-corosync/lib/puppet/provider/cs_primitive/pcs.rb
Line 263 in d868c5b
The text was updated successfully, but these errors were encountered: