Skip to content

OCPBUGS-24526,OPRUN-3182: Sync with upstream#654

Merged
openshift-merge-bot[bot] merged 4 commits intoopenshift:masterfrom
dtfranz:sync-with-upstream
Jan 10, 2024
Merged

OCPBUGS-24526,OPRUN-3182: Sync with upstream#654
openshift-merge-bot[bot] merged 4 commits intoopenshift:masterfrom
dtfranz:sync-with-upstream

Conversation

@dtfranz
Copy link
Copy Markdown
Contributor

@dtfranz dtfranz commented Jan 9, 2024 •
edited
Loading

Replaces #653 and #651

joelanford and others added 4 commits January 9, 2024 00:07
@joelanford
bump grpc to 1.60.1, reconnect idle connections (#3147)
58e1df3 
Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: e6d8fb022872af61bd34e80c185ff206d01dabcf
@dtfranz
Fix snapshot failure when catalogSourceNamespace does not contain Ope…
54fe93b 
…ratorGroup. (#3149)

Signed-off-by: Daniel Franz <dfranz@redhat.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 8eb16f7a9e12be729e07207983d27af78c23695b
@dependabot
build(deps): bump go.opentelemetry.io/contrib/instrumentation/google.…
71bf96f 
…golang.org/grpc/otelgrpc (#3150)

Bumps [go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc](https://github.com/open-telemetry/opentelemetry-go-contrib) from 0.44.0 to 0.46.0.
- [Release notes](https://github.com/open-telemetry/opentelemetry-go-contrib/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-go-contrib/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-go-contrib@zpages/v0.44.0...zpages/v0.46.0)

---
updated-dependencies:
- dependency-name: go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 4d6d11b6205312624f32be75c2df3b5d8837550a
@dtfranz
UPSTREAM: <carry>: Clean up replaces in go.mod
dc8c2a3 
Signed-off-by: dtfranz <dfranz@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 9, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jan 9, 2024 •
edited by openshift-ci Bot
Loading

@dtfranz: This pull request references OPRUN-3182 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 task to target the "4.16.0" version, but no target version was set.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jan 9, 2024 •
edited by openshift-ci Bot
Loading

@dtfranz: This pull request references OPRUN-3182 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 task to target the "4.16.0" version, but no target version was set.

Details

In response to this:

Replaces #653 and #650

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.

@dtfranz dtfranz mentioned this pull request Jan 9, 2024
Closed
@openshift-ci openshift-ci Bot requested review from awgreene and dinhxuanvu January 9, 2024 21:58
@dtfranz dtfranz changed the title OPRUN-3182: Sync with upstream OCPBUGS-24526,OPRUN-3182: Sync with upstream Jan 9, 2024
@openshift-ci-robot openshift-ci-robot added the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Jan 9, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jan 9, 2024 •
edited by openshift-ci Bot
Loading

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Xia-Zhao-rh

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references OPRUN-3182 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 task to target the "4.16.0" version, but no target version was set.

Details

In response to this:

Replaces #653 and #650

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 openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 9, 2024
@openshift-ci openshift-ci Bot requested a review from Xia-Zhao-rh January 9, 2024 21:59
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jan 9, 2024 •
edited by openshift-ci Bot
Loading

@dtfranz: This pull request references Jira Issue OCPBUGS-24526, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Xia-Zhao-rh

This pull request references OPRUN-3182 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 task to target the "4.16.0" version, but no target version was set.

Details

In response to this:

Replaces #653 and #651

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 Jan 9, 2024

@dtfranz: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test e2e-gcp-console-olm
  • /test e2e-gcp-olm
  • /test e2e-gcp-ovn
  • /test e2e-upgrade
  • /test images
  • /test periodics-images
  • /test unit-api
  • /test unit-olm
  • /test unit-psm
  • /test unit-registry
  • /test verify

The following commands are available to trigger optional jobs:

  • /test e2e-gcp-olm-flaky

Use /test all to run all jobs.

Details

In response to this:

Looks like cluster creation failed.
/retest e2e-gcp-olm
/retest e2e-gcp-console-olm

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.

@dtfranz
Copy link
Copy Markdown
Contributor Author

dtfranz commented Jan 10, 2024

/test e2e-gcp-console-olm
/test e2e-gcp-olm

@tmshort
Copy link
Copy Markdown
Contributor

tmshort commented Jan 10, 2024

/test e2e-upgrade

@tmshort
Copy link
Copy Markdown
Contributor

tmshort commented Jan 10, 2024

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jan 10, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 10, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dtfranz, tmshort

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

The pull request process is described 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 10, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jan 10, 2024

/retest-required

Remaining retests: 0 against base HEAD 743aeee and 2 for PR HEAD dc8c2a3 in total

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor

Xia-Zhao-rh commented Jan 10, 2024

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Jan 10, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jan 10, 2024 •
edited by openshift-ci Bot
Loading

@dtfranz: This pull request references Jira Issue OCPBUGS-24526, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Xia-Zhao-rh

This pull request references OPRUN-3182 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 task to target the "4.16.0" version, but no target version was set.

Details

In response to this:

Replaces #653 and #651

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.

@tmshort
Copy link
Copy Markdown
Contributor

tmshort commented Jan 10, 2024

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 10, 2024

@dtfranz: all tests passed!

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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot Bot merged commit 0081ef3 into openshift:master Jan 10, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jan 10, 2024

@dtfranz: Jira Issue OCPBUGS-24526: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-24526 has been moved to the MODIFIED state.

Details

In response to this:

Replaces #653 and #651

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

openshift-bot commented Jan 11, 2024

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-registry-container-v4.16.0-202401110907.p0.g0081ef3.assembly.stream for distgit operator-registry.
All builds following this will include this PR.

@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Jan 11, 2024

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-lifecycle-manager-container-v4.16.0-202401110907.p0.g0081ef3.assembly.stream for distgit operator-lifecycle-manager.
All builds following this will include this PR.

@dtfranz dtfranz mentioned this pull request Jan 23, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@awgreene awgreene Awaiting requested review from awgreene

@dinhxuanvu dinhxuanvu Awaiting requested review from dinhxuanvu

@Xia-Zhao-rh Xia-Zhao-rh Awaiting requested review from Xia-Zhao-rh

Assignees

@tmshort tmshort

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@dtfranz @openshift-ci-robot @tmshort @Xia-Zhao-rh @openshift-bot @joelanford