[release-4.15] OCPBUGS-36813: [CARRY] perform operator apiService certificate validity checks directly#819
Conversation
|
@ankitathomas: This pull request references Jira Issue OCPBUGS-36813, which is valid. 7 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request. 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: ankitathomas 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 |
…cks directly (#3217) * perform operator apiService certificate validity checks directly Signed-off-by: Ankita Thomas <ankithom@redhat.com> * use sets to track certs to install, revert to checking for installPlan timeouts after API availability checks, add service FQDN to list of hostnames. Signed-off-by: Ankita Thomas <ankithom@redhat.com> --------- Signed-off-by: Ankita Thomas <ankithom@redhat.com>
c2de061 to
1849397
Compare
|
/retest |
|
Test pass, see: https://issues.redhat.com/browse/OCPBUGS-36813 |
|
/label qe-approved |
|
/lgtm |
|
/retest |
|
/label backport-risk-assessed |
|
@ankitathomas: 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. |
|
@ankitathomas: Jira Issue OCPBUGS-36813: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-36813 has been moved to the MODIFIED state. 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. |
|
/cherry-pick release-4.14 |
|
@ankitathomas: #819 failed to apply on top of branch "release-4.14": 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. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build operator-lifecycle-manager-container-v4.15.0-202407112037.p0.g882fdf4.assembly.stream.el9 for distgit operator-lifecycle-manager. |
|
/cherry-pick release-4.14 |
|
@ankitathomas: #819 failed to apply on top of branch "release-4.14": 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. |
|
Fix included in accepted release 4.15.0-0.nightly-2024-07-12-193851 |
Manual cherry-pick of #798 to 4.15