Restore Error Return When Non-Leader Calls LeaderSettingsChanged #10301
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
This is a reversion of a single commit from #9353.
The commit logs a warning instead of returning an error when
LeaderSettingsChanged
is called by a non-leader unit.That commit should not have been retained in the patch, which ultimately focussed on re-checking leader status when preparing to fire the leader-elected hook.
QA steps
juju deploy ubuntu -n 2
juju run --unit <whichever is not the leader> leader-set
.ERROR cannot write leadership settings: cannot write settings: not the leader
.Documentation changes
None.
Bug reference
Original: https://bugs.launchpad.net/juju-core/+bug/1723184