I didn't spot an open PR on this, but there is open issue #485
It seems that the release of pacemaker 2.0.3 (in RHEL8) removes the option of supplying the superfluous score parameter.
Here is the documentation for pacemaker 2.0 which makes no mention of a score property:
https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Explained/s-resource-ordering.html
Pull Request (PR) description
Removes the score parameter from cs_order type as it is no longer valid and causes errors.
This Pull Request (PR) fixes the following issues
Fixes #485
<!--
Thank you for contributing to this project!
-->
Pull Request (PR) description
Update the command used to check config file for corosync v3+
This Pull Request (PR) fixes the following issues
RedHat/CentOS 8 support
Pull Request (PR) description
Sets CRM as the default provider for Ubuntu machines.
This Pull Request (PR) fixes the following issues
none (can create one if required)
I couldn't test the unit tests because of #536 It works in our environment though.
<!--
Thank you for contributing to this project!
-->
Pull Request (PR) description
Two core changes:
- Adds a clustered fact called corosync to determine the version of pcs
- Includes the node name for each entry in corosync.conf to correct a bug when running pcs cluster config
Pull Request (PR) description
The current code for authenticating to quorum members runs the auth command on every puppet run. This both updates the credentials on disk, and generates a puppet change event, which are btoh undesirable.
The proposed change checks to ensure all quorum members have an auth token in the credentials file, and updates auth for all members if any one member is missing. This results in a convergent state.
There is a caveat, in that what gets stored in the credentials file is not the original password, but an auth token. There does not seem to be a pcs command to check the tokens are still valid. So this code is only checking for presenence of auth tokens, not correctness. If the authentication token is later invalided, puppet will not correct this. It would be necessary to manually run the pcs host auth or pcs cluster auth commands to fix it.
This Pull Request (PR) fixes the following issues
Fixes #500
It is not possible to use transport: udpu and "cryptohash: none" or "cryptocipher: none" as it is not available as a parameter. I added it. UDPU doesnt support encryption and you are forced to use cryptohash or cryptocipher in corosync.conf (Version 3.x)
Pull Request (PR) description
This comment corrects the description for the newly introduced parameter param configvalidatecmd which was introduced with #508
This Pull Request (PR) fixes the following issues
Fixes a incorrect descrption of the parameter
Pull Request (PR) description
Rework of #484 against latest master branch.
The version of corosync uses a cli parameter instead of an environment variable to point at the config file to be tested. Without this change, the env var is ignored and the config_validate_cmd command always checks the real config file location before installing the candidate file. On a new build, this will fail because the real config file does not yet exist. When being updated, the real config file is checked, instead of the candidate file, so an invalid change might be falsely reported as acceptable and lead to an outage.
This change overrides the config validate command on el8 to use the correct syntax.
It also lists el8 as a compatible OS in the module metadata, since the module is currently being used with this patch in production.
This Pull Request (PR) fixes the following issues
Fixes #526
Obsoletes #484
