Skip to content
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

OCPBUGS-13910: update community-operator-index to 4.14 tag #524

Merged
merged 1 commit into from Jun 22, 2023
Merged

OCPBUGS-13910: update community-operator-index to 4.14 tag #524

merged 1 commit into from Jun 22, 2023

Conversation

everettraven
Copy link
Contributor

Description of the change:

  • Updates the community operator index image to use the 4.14 tag

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /docs
  • Commit messages sensible and descriptive

@everettraven
update community-operator-index to 4.14 tag
4d9a501 
Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
@openshift-ci-robot openshift-ci-robot added 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 Jun 20, 2023
@openshift-ci-robot
Copy link
Contributor

@everettraven: This pull request references Jira Issue OCPBUGS-13910, 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.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

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

In response to this:

Description of the change:

  • Updates the community operator index image to use the 4.14 tag

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /docs
  • Commit messages sensible and descriptive

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.

@oceanc80
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 20, 2023
anik120
anik120 approved these changes Jun 20, 2023
View reviewed changes
Copy link
Contributor

@anik120 anik120 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment from https://issues.redhat.com/browse/ISV-3664

The 4.14 index has been published.
Now working on unblocking the release of new PRs.

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 20, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, everettraven

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 20, 2023
@everettraven
Copy link
Contributor Author

/retest-required

2 similar comments
@everettraven
Copy link
Contributor Author

/retest-required

@everettraven
Copy link
Contributor Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 21, 2023 •
edited

@everettraven: 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/okd-scos-e2e-gcp 4d9a501 link false /test okd-scos-e2e-gcp
ci/prow/okd-e2e-gcp 4d9a501 link false /test okd-e2e-gcp

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.

@anik120
Copy link
Contributor

anik120 commented Jun 22, 2023

/test e2e-aws-ovn-serial

@openshift-merge-robot openshift-merge-robot merged commit 06e150e into operator-framework:master Jun 22, 2023
10 of 12 checks passed
@openshift-ci-robot
Copy link
Contributor

@everettraven: Jira Issue OCPBUGS-13910: All pull requests linked via external trackers have merged:

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

In response to this:

Description of the change:

  • Updates the community operator index image to use the 4.14 tag

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /docs
  • Commit messages sensible and descriptive

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.

@KeenonLee
Copy link
Contributor

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jun 25, 2023
KeenonLee
KeenonLee reviewed Jun 25, 2023
View reviewed changes
Copy link
Contributor

@KeenonLee KeenonLee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@KeenonLee KeenonLee KeenonLee left review comments

@anik120 anik120 anik120 approved these changes

@awgreene awgreene Awaiting requested review from awgreene

@grokspawn grokspawn Awaiting requested review from grokspawn

Assignees

@oceanc80 oceanc80

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

None yet
6 participants
@everettraven @openshift-ci-robot @oceanc80 @anik120 @KeenonLee @openshift-merge-robot