Skip to content

[release-4.15] OCPBUGS-36813: perform operator apiService certificate validity checks directly#818

Closed
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.15from
openshift-cherrypick-robot:cherry-pick-798-to-release-4.15
Closed

[release-4.15] OCPBUGS-36813: perform operator apiService certificate validity checks directly#818
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.15from
openshift-cherrypick-robot:cherry-pick-798-to-release-4.15

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jul 10, 2024

This is an automated cherry-pick of #798

/assign ankitathomas

@ankitathomas
perform operator apiService certificate validity checks directly (#3217)
81705a0 
* 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>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jul 10, 2024
Merged
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 10, 2024

@openshift-cherrypick-robot: Jira Issue OCPBUGS-36138 has been cloned as Jira Issue OCPBUGS-36813. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-36813: perform operator apiService certificate validity checks directly

Details

In response to this:

This is an automated cherry-pick of #798

/assign ankitathomas

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 openshift-ci Bot changed the title [release-4.15] OCPBUGS-36138: perform operator apiService certificate validity checks directly [release-4.15] OCPBUGS-36813: perform operator apiService certificate validity checks directly Jul 10, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jul 10, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 10, 2024

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-36813, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-36138 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-36138 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
  • bug has dependents

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.

Details

In response to this:

This is an automated cherry-pick of #798

/assign ankitathomas

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 openshift-ci Bot requested review from dinhxuanvu and perdasilva July 10, 2024 13:17
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 10, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please ask for approval from ankitathomas. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ankitathomas
Copy link
Copy Markdown
Contributor

ankitathomas commented Jul 10, 2024 •
edited
Loading

closing in favor of #819

@ankitathomas
Copy link
Copy Markdown
Contributor

ankitathomas commented Jul 10, 2024

/close

@openshift-ci openshift-ci Bot closed this Jul 10, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 10, 2024

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-36813. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #798

/assign ankitathomas

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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 10, 2024

@ankitathomas: Closed this PR.

Details

In response to this:

/close
closing in favor of #819

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 10, 2024

@ankitathomas: Closed this PR.

Details

In response to this:

/close

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 10, 2024

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/verify 81705a0 link true /test verify
ci/prow/unit-olm 81705a0 link true /test unit-olm

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dinhxuanvu dinhxuanvu Awaiting requested review from dinhxuanvu

@perdasilva perdasilva Awaiting requested review from perdasilva

Assignees

@ankitathomas ankitathomas

Labels

jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@openshift-cherrypick-robot @openshift-ci-robot @ankitathomas