Information on udpu seems not totally clear and doc is missing any mention of Knet

[AndreasPfaffeneder]

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 6.21.1
• Ruby: 2.5.5p157
• Distribution: RHEL 8.4
• Module version: v8.0.0

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:

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.

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