OPECO-3066: Synchronize From Upstream Repositories #612
Conversation
openshift-bot
added
approved
|
@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-ecosystem. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. In 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/test-infra repository. |
|
[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 |
1 similar comment
|
[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 |
|
It appears that cluster installation failed, not a flake. /retest |
Signed-off-by: Alexander Greene <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: db965b08107161d0da95f52db6365d9fc78c6118
Signed-off-by: Alexander Greene <[email protected]> Co-authored-by: Kevin Rizza <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: e7debb4631cc1607180a57f73da686a075a38a50
Signed-off-by: Alexander Greene <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 4655321370258ac76e194b027d845a8154a74ae2
The previous approach here was to use go-spew, which, unfortunately, is not a stable and germane encoding for objects. We are encoding objects that we send to the Kubernetes API server, so features of go-spew like printing the capacity of slices are not germane. This led to hashes of otherwise identical (as far as the server was concerned) objects to be determined as hashing differently. Signed-off-by: Steve Kuznetsov <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 658a6a60de8315f055f54aa7e50771ee4daa8983
At the time of making this commit, the package `github.com/ghodss/yaml` is no longer actively maintained. `sigs.k8s.io/yaml` is a permanent fork of `ghodss/yaml` and is actively maintained by Kubernetes SIG. Signed-off-by: Eng Zer Jun <[email protected]> Upstream-repository: api Upstream-commit: 5efe1a23d8c21e51c6a63a472a0d5320342187ec
* deprecations unit tests Signed-off-by: Jordan Keister <[email protected]> * review updates Signed-off-by: Jordan Keister <[email protected]> * dogmatic review updates Signed-off-by: Jordan Keister <[email protected]> --------- Signed-off-by: Jordan Keister <[email protected]> Upstream-repository: operator-registry Upstream-commit: 39df3b78e77574c64cc05e480cbd6fe83cf2b428
openshift-bot
force-pushed
the
synchronize-upstream
branch
from
2fb0d0f to
d663a0d
Compare
|
/lgtm |
ncdc
added
the
acknowledge-critical-fixes-only
|
/retitle OPECO-3066: Synchronize From Upstream Repositories |
openshift-ci
bot
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@openshift-bot: This pull request references OPECO-3066 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. In 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/test-infra repository. |
|
Two failures: We've seen one of these before. |
|
@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/test-infra repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build operator-registry-container-v4.15.0-202311172250.p0.g639fc12.assembly.stream for distgit operator-registry. |
The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:
github.com/ghodss/yamlwithsigs.k8s.io/yaml(#308)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