-
Notifications
You must be signed in to change notification settings - Fork 88
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
chore: Add logger to track reconcilers invocation #1921
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tolusha The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Anatolii Bazko <[email protected]>
Signed-off-by: Anatolii Bazko <[email protected]>
Signed-off-by: Anatolii Bazko <[email protected]>
Signed-off-by: Anatolii Bazko <[email protected]>
@tolusha: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Build 3.18 :: operator_3.x/416: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7832: Console, Changes, Git Data |
Build 3.18 :: push-latest-container-to-quay_3.x/4996: Console, Changes, Git Data |
Build 3.18 :: get-sources-rhpkg-container-build_3.x/7844: devspaces-operator : 3.x :: Build 65178426 : quay.io/devspaces/devspaces-rhel8-operator:3.18-9 |
Build 3.18 :: operator_3.x/416: Upstream sync done; /DS_CI/sync-to-downstream_3.x/7832 triggered |
Build 3.18 :: update-digests_3.x/7786: Console, Changes, Git Data |
Build 3.18 :: operator-bundle_3.x/3668: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7833: Console, Changes, Git Data |
Build 3.18 :: push-latest-container-to-quay_3.x/4997: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7833: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.x/7845 triggered; /job/DS_CI/job/dsc_3.x triggered; |
Build 3.18 :: operator-bundle_3.x/3668: Upstream sync done; /DS_CI/sync-to-downstream_3.x/7833 triggered |
Build 3.18 :: copyIIBsToQuay/2858: Console, Changes, Git Data |
Build 3.18 :: dsc_3.x/2028: Console, Changes, Git Data |
Build 3.18 :: update-digests_3.x/7786: Detected new images: rebuild operator-bundle |
Build 3.18 :: dsc_3.x/2028: 3.18.0-CI |
Build 3.18 :: copyIIBsToQuay/2858: 3.18 |
Build 3.18 :: operator-bundle_3.x/3671: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7842: Console, Changes, Git Data |
Build 3.18 :: get-sources-rhpkg-container-build_3.x/7854: devspaces-operator-bundle : 3.x :: Failed in 65206015 : BREW:BUILD/STATUS:UNKNOWN |
Build 3.18 :: operator-bundle_3.x/3672: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7843: Console, Changes, Git Data |
Build 3.18 :: get-sources-rhpkg-container-build_3.x/7855: devspaces-operator-bundle : 3.x :: Failed in 65210138 : BREW:BUILD/STATUS:UNKNOWN |
Build 3.18 :: operator-bundle_3.x/3673: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7844: Console, Changes, Git Data |
Build 3.18 :: get-sources-rhpkg-container-build_3.x/7856: devspaces-operator-bundle : 3.x :: Failed in 65212817 : BREW:BUILD/STATUS:UNKNOWN |
Build 3.18 :: operator-bundle_3.x/3674: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7845: Console, Changes, Git Data |
Build 3.18 :: get-sources-rhpkg-container-build_3.x/7857: devspaces-operator-bundle : 3.x :: Failed in 65215827 : BREW:BUILD/STATUS:UNKNOWN |
What does this PR do?
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
eclipse-che/che#23167
How to test this PR?
OpenShift
on Minikube
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.