We can add some error handling into the ceph charm to catch this type of
problem so that a single bad disk does not block an entire deployment;
however I'm concerned that there is not currently a good way to
propagate this back up to the end user (other than erroring the hook as
currently happens).
We need a way to propagate warnings about things which are not blocking
deployment but need to be investigated/responded to IMHO.
** Also affects: ceph-osd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ceph (Juju Charms Collection)
Status: New => Triaged
** Changed in: ceph-osd (Ubuntu)
Status: New => Triaged
** Changed in: ceph (Juju Charms Collection)
Importance: Undecided => High
** Changed in: ceph-osd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1343199
Title:
Ceph charms die horribly when the device behaves badly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph-osd/+bug/1343199/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
