Feature #53140
open
HEALTH_WARN about known issues of running version
Added by Dan van der Ster over 2 years ago.
Updated over 2 years ago.
Description
If the running version has a known issue (of configurable severity?), issue a health warning.
The proposed implementation would query an xml or json of known issues, keyed by version e.g. 16.2.6-0.
Related issues
1 (1 open — 0 closed)
+1
David Orman also suggested requiring a manual override to install a "pulled" version once that version has been flagged.
There's going to be a new mgr module called 'feedback' for users to report Ceph issues from the CLI and UI.
Given that's basically a wrapper around Redmine, we could use it to regularly (daily) poll Redmine and trigger a Healthcheck error if an issue with "severity = critital" affects the version the cluster is running. The main downside of this would be DDoS (it seems that Redmine has some built-in cache).
- Related to Feature #53320: cephadm: warn users before upgrading to a release with major bugs in it added
I think this needs to have an "acknowledge" functionality so it doesn't persist to cause warnings.
Given the motivating case, we want to warn users not to enable the bluestone omap fsck, but once they have that information they should not continue getting warned.
Also available in: Atom
PDF