Comment 18 for bug 1876849

Thanks for the feedback, @dmitriis. I agree that this puts a burden on the charm author, and it would be nicer to have Juju abstract it away.

I don't think that the field high label is appropriate, however. In the field, timing issues with the profile being applied should get resolved via a retry. This issue seems to be uniquely damaging in a testing environment with retry turned off, while testing a charm that was written with incorrect assumptions about the way that the profile watcher currently works.

I think that the next steps here are to treat this like a feature request, and add it to the list of things in consideration for the roadmap. The scope of the feature is to redesign the profile watcher so that it can behave more linearly. This is a non trivial chunk of work, involving an approach which was initially considered and then discarded by the Juju team, which merits a more complete discussion of the tradeoffs involved.