-
Notifications
You must be signed in to change notification settings - Fork 160
OCPBUGS-74384: Resolve nil pointer exception in hasResourceTags #966
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
base: master
Are you sure you want to change the base?
Conversation
|
@jstuever: This pull request references Jira Issue OCPBUGS-74384, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this: 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jstuever The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/jira backport release-4.21,release-4.20,release-4.19,release-4.18,release-4.17 |
|
@jstuever: The following backport issues have been created:
Queuing cherrypicks to the requested branches to be created after this PR merges: DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@openshift-ci-robot: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
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. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #966 +/- ##
=======================================
Coverage 46.48% 46.48%
=======================================
Files 98 98
Lines 12181 12181
=======================================
Hits 5662 5662
Misses 5869 5869
Partials 650 650
🚀 New features to boost your workflow:
|
|
/test e2e-aws-ovn |
|
@jstuever: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
I've reproduced the issue on vsphere(4.20.0-0.nightly-2026-01-26-202217). (2)duplicate another infrastructure object, rename cloud-provider-config and remove the whole .status part jshu@jshu-mac % oc get pods -n openshift-cloud-credential-operator -w Pod error: |
|
jshu@jshu-mac % oc get infrastructure Remove "infrastructure cloud-provider-config" can make the cluster back to normal. It could be workaround. @jstuever Shall we change the code to read the record of "infrastructure cluster" only in this PR or a follow-up PR? |
|
/verified by @jianping-shu If had further code change, I'll re-verify. |
|
@jianping-shu: This PR has been marked as verified by DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@jianping-shu I would prefer a follow-up PR as that will take (slightly) more effort to resolve. Would you open a new bug so we can track it? |
|
/assign @dlom |
|
Created OCPBUGS-74627 for infrastructure record issue. |
No description provided.