Fix corosync 3.x startup failure on SLE 16.0#464
Merged
Conversation
Fix corosync by omitting invalid config options. Corosync 3.x (shipped in SLE 16.0) rejects crypto_cipher, crypto_hash, and secauth when transport is udpu, causing corosync to exit with code 8 and pacemaker to fail on its dependency. These options are safe to omit because they were never functional with udpu transport — corosync 2.x silently accepted them but only supported encryption on multicast (UDP) transport. Cluster traffic was never encrypted with udpu, so removing these options changes no runtime behavior. Similarly, rrp_mode (removed in corosync 3.x) had no effect with a single interface. The version conditional preserves the existing config for corosync 2.x (SLE 12 SP5, SLE 15 SP4/SP5) and only omits the options on 3.x+.
Collaborator
|
LGTM, thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix corosync by omitting invalid config options.
Corosync 3.x (shipped in SLE 16.0) rejects crypto_cipher, crypto_hash, and secauth when transport is udpu, causing corosync to exit with code 8 and pacemaker to fail on its dependency.
These options are safe to omit because they were never functional with udpu transport — corosync 2.x silently accepted them but only supported encryption on multicast (UDP) transport. Cluster traffic was never encrypted with udpu, so removing these options changes no runtime behavior. Similarly, rrp_mode (removed in corosync 3.x) had no effect with a single interface.
The version conditional preserves the existing config for corosync 2.x (SLE 12 SP5, SLE 15 SP4/SP5) and only omits the options on 3.x+.
Ticket: https://jira.suse.com/browse/TEAM-11163
Verification:
16.0
sle-16.0-Qesap-Gcp-Payg-x86_64-BuildLATEST_GCE_SLE16_0-qesap_gcp_angi_test
sle-16.0-HanaSr-Aws-Payg-x86_64-Build16.0_2026-04-22T02:03:26Z-hanasr_aws_test_fencing_native_stop_kill ec2_r4.8xlarge
sle-16.0-HanaSr-Azure-Byos-x86_64-Build16.0_2026-04-22T02:03:26Z-hanasr_azure_test_msi az_Standard_E4s_v3
sle-16.0-HanaSr-Gcp-Byos-x86_64-Build16.0_2026-04-22T02:03:26Z-hanasr_gcp_test_fencing_native_stop_kill gce_n1_highmem_32
Not 16.0
sle-12-SP5-Qesap-Aws-Payg-x86_64-BuildLATEST_AWS_SLE12_5-qesap_aws_saptune_ltss_test
corosync: release:"9.22.1" version:"2.3.6"