Oops, I hit send a bit too early. I wanted to ask if this is by design or if it's worth a bug report. Thanks Eugen Zitat von Eugen Block <eblock@nde.ag>:
Hi,
I just tested the upgrade from a single-node mini cluster (only mgr and mon daemons) bootstrapped with 19.2.6 to 20.2.4. After the bootstrap I have no warnings (except that I don't have any OSDs), this is the excerpt from the mon dump:
min_mon_release 19 (squid) election_strategy: 1 0: [v2:192.168.124.6:3300/0,v1:192.168.124.6:6789/0] mon.tentacle auth_epoch 0 auth_service_cipher aes256k auth_allowed_ciphers aes256k auth_preferred_cipher aes256k
After the upgrade to 20.2.4 the mon dump looks like this (look at auth_allowed_ciphers):
min_mon_release 20 (tentacle) election_strategy: 1 0: [v2:192.168.124.6:3300/0,v1:192.168.124.6:6789/0] mon.tentacle auth_epoch 0 auth_service_cipher aes256k auth_allowed_ciphers aes, aes256k auth_preferred_cipher aes256k
Obviously, the cluster now warns about the MONs allowing insecure keys:
Monitors are configured to allow auth using insecure key types Monitors are configured to allow creation of insecure key types