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.

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

OCPBUGS-29415: Synchronize the periodic build images to the release images #48714

Merged
merged 1 commit into from
Feb 13, 2024

Conversation

tmshort
Copy link
Contributor

@tmshort tmshort commented Feb 12, 2024

No description provided.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 12, 2024
@tmshort
Copy link
Contributor Author

tmshort commented Feb 12, 2024

/pj-rehearse rehearse-ack

@openshift-ci-robot
Copy link
Contributor

@tmshort: job(s): rehearse-ack either don't exist or were not found to be affected, and cannot be rehearsed

Signed-off-by: Todd Short <todd.short@me.com>
@tmshort
Copy link
Contributor Author

tmshort commented Feb 12, 2024

/pj-rehearse auto-ack

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@tmshort: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-operator-framework-olm-release-4.15-periodics-images openshift/operator-framework-olm presubmit Ci-operator config changed
periodic-ci-openshift-operator-framework-olm-release-4.15-periodics-e2e-gcp-olm N/A periodic Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

Copy link
Contributor

openshift-ci bot commented Feb 12, 2024

@tmshort: The following test 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/rehearse/periodic-ci-openshift-operator-framework-olm-release-4.15-periodics-e2e-gcp-olm 5afd4ac link unknown /pj-rehearse periodic-ci-openshift-operator-framework-olm-release-4.15-periodics-e2e-gcp-olm

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.

@joelanford
Copy link
Member

/retitle "OCPBUGS-29415: Synchronize the periodic build images to the release images"

@tmshort tmshort changed the title Synchronize the periodic build images to the release images OCPBUGS-29415: Synchronize the periodic build images to the release images Feb 13, 2024
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 13, 2024
@openshift-ci-robot
Copy link
Contributor

@tmshort: This pull request references Jira Issue OCPBUGS-29415, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

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.

@tmshort
Copy link
Contributor Author

tmshort commented Feb 13, 2024

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@tmshort: This pull request references Jira Issue OCPBUGS-29415, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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
Contributor Author

tmshort commented Feb 13, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 13, 2024
@openshift-ci-robot
Copy link
Contributor

@tmshort: This pull request references Jira Issue OCPBUGS-29415, 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 New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jianzhangbjz

In response to this:

/jira refresh

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
Contributor Author

tmshort commented Feb 13, 2024

/pj-rehearse ack
The test failure is a known flake:

Install Plan with deprecated version CRD Test [It] upgrade CRD with deprecated version

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 13, 2024
@kevinrizza
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 13, 2024
Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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-merge-bot openshift-merge-bot bot merged commit bceb07d into openshift:master Feb 13, 2024
17 of 18 checks passed
@openshift-ci-robot
Copy link
Contributor

@tmshort: Jira Issue OCPBUGS-29415: All pull requests linked via external trackers have merged:

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

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.

mshitrit pushed a commit to mshitrit/release that referenced this pull request Feb 14, 2024
shaior pushed a commit to natifridman/release that referenced this pull request Feb 14, 2024
sgoveas pushed a commit to sgoveas/release that referenced this pull request Feb 22, 2024
memodi pushed a commit to memodi/release that referenced this pull request Mar 14, 2024
@tmshort tmshort deleted the fix-olm-images branch June 13, 2024 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged
Projects
None yet
4 participants