Conversation
…it_status misuses Agent-Logs-Url: https://github.com/canonical/mysql-operators/sessions/9dc045f5-e998-405f-918e-299a250ed5ef Co-authored-by: astrojuanlu <316517+astrojuanlu@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
astrojuanlu
April 23, 2026 12:00
View session
This comment was marked as outdated.
This comment was marked as outdated.
Copilot
AI
force-pushed
the
copilot/backport-pr-264-to-8-0-edge
branch
from
April 23, 2026 12:04
fb69108 to
33d0f4d
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
astrojuanlu
added
the
not bug or enhancement
github-actions
Bot
added
the
Libraries: Out of sync
2 tasks
Contributor
sinclert-canonical
left a comment
sinclert-canonical
left a comment
There was a problem hiding this comment.
Same comments as in the 8.4/edge one.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #264 to the
8.0/edgebranch.Issue
The self-healing setup crash test has always been broken: it was checking the app status instead of the workload status when waiting for units to enter the "waiting" phase. Additionally, several roles tests had misuses of
wait_for_unit_statuswhere the returned lambda was not being called withstatus.Solution
test_self_healing_setup_crash.py:wait_for_unit_statusto importstrust=Trueto thejuju.deploy()callsuccesses=1to mitigate race conditions if units clear the "waiting" phase too quicklytest_database_dba_role.py,test_instance_dba_role.py,test_instance_roles.py: Fixed misuses ofwait_for_unit_status— the function returns a lambda that must be called with(status).Checklist