Skip to content

NO-ISSUE: Synchronize From Upstream Repositories #801

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 5 commits into from
Jun 27, 2024
Merged

NO-ISSUE: Synchronize From Upstream Repositories #801

merged 5 commits into from
Jun 27, 2024

Conversation

openshift-bot
Copy link
Contributor

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2024-06-20 15:19:53 operator-framework/operator-lifecycle-manager@908da0c Ankita Thomas [OCPBUGS-25341]: perform operator apiService certificate validity checks directly (#3217)
2024-06-26 14:24:40 operator-framework/operator-lifecycle-manager@63a2293 Per Goncalves da Silva Bump kubeapis to 0.30.2 (#3329)
2024-06-26 16:44:00 operator-framework/operator-lifecycle-manager@5d32045 Per Goncalves da Silva make flake attempts an optional parameter (#3330)
2024-06-26 17:48:08 operator-framework/operator-lifecycle-manager@75c3f58 Per Goncalves da Silva drop --show-node-events from e2e call (#3331)
2024-06-26 17:59:10 operator-framework/operator-lifecycle-manager@b8fb628 Per Goncalves da Silva build(deps): bump k8s.io/component-base from 0.30.1 to 0.30.2 (#3320) (#3293)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem

ankitathomas and others added 5 commits June 27, 2024 00:01
@ankitathomas
[OCPBUGS-25341]: perform operator apiService certificate validity che…
20de594 
…cks directly (#3217)

* perform operator apiService certificate validity checks directly

Signed-off-by: Ankita Thomas <[email protected]>

* 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 <[email protected]>

---------

Signed-off-by: Ankita Thomas <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 908da0c05363da40ad09ab774d9904b22aca7869
@perdasilva
Bump kubeapis to 0.30.2 (#3329)
bb9eff2 
Signed-off-by: Per Goncalves da Silva <[email protected]>
Co-authored-by: Per Goncalves da Silva <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 63a2293b9b1bb5c48d30f6362bc9c04bc2ed1d1e
@perdasilva
make flake attempts an optional parameter (#3330)
50ccd40 
Signed-off-by: Per Goncalves da Silva <[email protected]>
Co-authored-by: Per Goncalves da Silva <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 5d32045dbe4f65526264f6115bff748d340a7cab
@perdasilva
drop --show-node-events from e2e call (#3331)
9d75781 
Signed-off-by: Per Goncalves da Silva <[email protected]>
Co-authored-by: Per Goncalves da Silva <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 75c3f583056548eae4c39c4e918789d6a9ced70b
@perdasilva @dependabot
build(deps): bump k8s.io/component-base from 0.30.1 to 0.30.2 (#3320)…
5274dd9 
… (#3293)

Bumps [k8s.io/component-base](https://github.com/kubernetes/component-base) from 0.30.1 to 0.30.2.
- [Commits](kubernetes/component-base@v0.30.1...v0.30.2)

Upstream-repository: operator-lifecycle-manager
Upstream-commit: b8fb628f6eae82d8a036e90b57bf61bd4e88761a

---
updated-dependencies:
- dependency-name: k8s.io/component-base
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: Per Goncalves da Silva <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@openshift-bot openshift-bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels Jun 27, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 27, 2024
@openshift-ci-robot
Copy link

@openshift-bot: This pull request explicitly references no jira issue.

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2024-06-20 15:19:53 operator-framework/operator-lifecycle-manager@908da0c Ankita Thomas [OCPBUGS-25341]: perform operator apiService certificate validity checks directly (#3217)
2024-06-26 14:24:40 operator-framework/operator-lifecycle-manager@63a2293 Per Goncalves da Silva Bump kubeapis to 0.30.2 (#3329)
2024-06-26 16:44:00 operator-framework/operator-lifecycle-manager@5d32045 Per Goncalves da Silva make flake attempts an optional parameter (#3330)
2024-06-26 17:48:08 operator-framework/operator-lifecycle-manager@75c3f58 Per Goncalves da Silva drop --show-node-events from e2e call (#3331)
2024-06-26 17:59:10 operator-framework/operator-lifecycle-manager@b8fb628 Per Goncalves da Silva build(deps): bump k8s.io/component-base from 0.30.1 to 0.30.2 (#3320) (#3293)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem

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

openshift-ci bot commented Jun 27, 2024

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

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

The pull request process is described here

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

1 similar comment
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 27, 2024

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

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

The pull request process is described here

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

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 02e3f41 and 2 for PR HEAD 5274dd9 in total

@perdasilva
Copy link
Contributor

/retest

1 similar comment
@tmshort
Copy link
Contributor

tmshort commented Jun 27, 2024

/retest

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 27, 2024

@openshift-bot: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 63f1343 into openshift:master Jun 27, 2024
13 checks passed
@openshift-bot
Copy link
Contributor Author

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-registry-container-v4.17.0-202406280739.p0.g63f1343.assembly.stream.el9 for distgit operator-registry.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@openshift-bot @openshift-ci-robot @perdasilva @tmshort @ankitathomas