-
Notifications
You must be signed in to change notification settings - Fork 180
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
Log MIWI/SP install type to AsyncQoS; also log successful cluster deletions #3934
Merged
cadenmarchese
merged 2 commits into
master
from
ventifus/ARO-11772-log-delete-completion
Jan 27, 2025
Merged
Log MIWI/SP install type to AsyncQoS; also log successful cluster deletions #3934
cadenmarchese
merged 2 commits into
master
from
ventifus/ARO-11772-log-delete-completion
Jan 27, 2025
Conversation
This file contains 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
/azp run ci,e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
In the e2e logs for deletion, it does not appear to delete via backend operation, so it's not testing this change. |
edisonLcardenas
previously approved these changes
Nov 5, 2024
bitoku
previously approved these changes
Nov 7, 2024
Please rebase pull request. |
16a54b5
to
8b8aecf
Compare
/azp run e2e,ci |
Azure Pipelines successfully started running 2 pipeline(s). |
rajdeepc2792
approved these changes
Jan 24, 2025
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.
lgtm, thank you!!
cadenmarchese
approved these changes
Jan 24, 2025
s-fairchild
approved these changes
Jan 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
chainsaw
Pull requests or issues owned by Team Chainsaw
next-release
To be included in the next RP release rollout
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.
Which issue this PR addresses:
Fixes https://issues.redhat.com/browse/ARO-11772
Enables https://issues.redhat.com/browse/ARO-7841
What this PR does / why we need it:
For dashboarding purposes, we're missing a few things:
We wish to include cluster deletion success/failure rates in a dashboard. This is not possible because currently we don't log the completion of successful cluster deletions. That's because the logs (and other metrics) get emitted by endLease(), and the lease doesn't get released for deletions because the cluster doc gets deleted instead.
We wish to improve our cluster creation dashboards by distinguishing MIWI clusters installs from Service Principal installs. To do that we need a new field in AsyncQoS that records the cluster identity type requested.
Test plan for issue:
Manual testing will be required, as E2E does not exercise this as part of cluster deletion.
When manually testing, check that the appropriate "long running operation succeeded" log is emitted for cluster creation. Check that "long running operation succeeded" now gets logged on deletion. Check that the
clusterIdentity
field is emitted in AsyncQoS logs.Is there any documentation that needs to be updated for this PR?
How do you know this will function as expected in production?