From a charm's perspective, I believe we should be setting [DEFAULT].unknown_config_option to "warning", so (possible) future changes in this area won't break a running cluster.
From the docs https://dev.mysql.com/doc/mysql-router/8.0/en/mysql-router-conf-options.html#option_mysqlrouter_unknown_config_option : """ A warning is default behavior, and bootstrapping defines it as error in the generated configuration file. MySQL Router versions before 8.0.29 ignore unknown configuration options. A warning logs a warning message but does not halt, whereas an error means Router fails to initialize and exits. """ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971565 Title: charm no longer works with latest mysql-router version To manage notifications about this bug go to: https://bugs.launchpad.net/charm-mysql-router/+bug/1971565/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
