-
Notifications
You must be signed in to change notification settings - Fork 36
[DPE-10454] Use better status instead of blocked for transient update failures #1795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
taurus-forever
wants to merge
1
commit into
16/edge
Choose a base branch
from
alutay/polish_blocked
base: 16/edge
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2233,11 +2233,12 @@ def test_on_peer_relation_changed(harness): | |
| _update_config.assert_called_once() | ||
| _start_patroni.assert_not_called() | ||
| _update_new_unit_status.assert_not_called() | ||
| assert isinstance(harness.model.unit.status, BlockedStatus) | ||
| assert isinstance(harness.model.unit.status, MaintenanceStatus) | ||
|
|
||
| # Test event is early exiting when in blocked status. | ||
| _update_config.side_effect = None | ||
| _member_started.return_value = False | ||
| harness.model.unit.status = BlockedStatus() | ||
| harness.charm._on_peer_relation_changed(mock_event) | ||
| _start_patroni.assert_not_called() | ||
|
|
||
|
|
@@ -2526,8 +2527,8 @@ def test_add_cluster_member(harness): | |
| _update_config.side_effect = RetryError(last_attempt=None) | ||
| harness.charm.add_cluster_member("postgresql-0") | ||
| _update_config.assert_called_once_with() | ||
| assert isinstance(harness.charm.unit.status, BlockedStatus) | ||
| assert harness.charm.unit.status.message == "failed to update cluster members on member" | ||
| assert isinstance(harness.charm.unit.status, MaintenanceStatus | WaitingStatus) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Better to assert the exact status we are expecting here. |
||
| assert harness.charm.unit.status.message == "pending update cluster members on member" | ||
| _update_config.reset_mock() | ||
|
|
||
| # Not ready error if not all members are ready | ||
|
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using WaitingStatus here as a flag to recognize RetryError==MaintenanceStatus.
Should I sync all to the same status?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if we have something like
WaitingStatus("waiting for peer IP")here andMaintenanceStatus("updating cluster members")in L1415 and L1196 to make the status messages correspond to each state?