Closed AndreasPfaffeneder closed 3 years ago
Use existing configuration of from systems with corosync 2.x on a system with corosync 3.x.
e.g:
class {'corosync': authkey_source => $authkey_source, authkey => $authkey, ... unicast_addresses => $unicast_addresses }
This leads, due to the changes in corosync, to a not working configuration.
Validate of configuration fails/Corosync not able to start.
Some hint in the documentation that Knet supersedes udpu in Corosync 3.x.
parse error in config: crypto_cipher & crypto_hash are only valid for the Knet transport
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Use existing configuration of from systems with corosync 2.x on a system with corosync 3.x.
e.g:
This leads, due to the changes in corosync, to a not working configuration.
What are you seeing
Validate of configuration fails/Corosync not able to start.
What behaviour did you expect instead
Some hint in the documentation that Knet supersedes udpu in Corosync 3.x.
Output log
parse error in config: crypto_cipher & crypto_hash are only valid for the Knet transport
Any additional information you'd like to impart