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-46532: bump OPCT to v0.5.1 #60205

Merged
merged 1 commit into from
Dec 30, 2024
Merged

OCPBUGS-46532: bump OPCT to v0.5.1 #60205

merged 1 commit into from
Dec 30, 2024

Conversation

mtulio
Copy link
Contributor

@mtulio mtulio commented Dec 29, 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 Dec 29, 2024
@openshift-ci-robot
Copy link
Contributor

@mtulio: This pull request references Jira Issue OCPBUGS-46532, which is invalid:

  • expected the bug to target the "4.19.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:

Bump OPCT for bug fixes.
Ref:

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.

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

/assign @rvanderp3

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@mtulio: This pull request references Jira Issue OCPBUGS-46532, which is invalid:

  • expected the bug to target the "4.19.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.

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@mtulio: 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-assisted-test-infra-master-opct-oci-assisted-4-18 openshift/assisted-test-infra presubmit Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.18-platform-none-vsphere N/A periodic Registry content changed
periodic-ci-openshift-assisted-test-infra-master-opct-oci-assisted-4-18-periodic N/A periodic Registry content changed
periodic-ci-openshift-release-master-nightly-4.18-opct-external-aws-ccm N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.17-platform-none-vsphere N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.15-platform-none-vsphere N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.16-platform-external-vsphere-upgrade N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.17-platform-external-vsphere N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.17-platform-external-vsphere-upgrade N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.15-platform-none-vsphere-upgrade N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.18-platform-external-vsphere N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.16-platform-external-vsphere N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.15-platform-external-vsphere N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.16-platform-none-vsphere-upgrade N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.17-platform-none-vsphere-upgrade N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.16-platform-none-vsphere N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.14-platform-external-vsphere N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.14-platform-none-vsphere-upgrade N/A periodic Registry content changed
periodic-ci-openshift-release-master-nightly-4.16-opct-external-aws-ccm N/A periodic Registry content changed
periodic-ci-openshift-release-master-nightly-4.17-opct-external-aws-ccm N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.15-platform-external-vsphere-upgrade N/A periodic Registry content changed
periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws-ccm N/A periodic Registry content changed
periodic-ci-redhat-openshift-ecosystem-opct-main-4.14-platform-none-vsphere N/A periodic Registry content changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

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
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

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.

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

PTAL?
/assign @adriengentil @deepsm007

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

Hold until rehearsal finishes:
/hold
/pj-rehearse auto-ack

@openshift-ci-robot
Copy link
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 29, 2024
@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 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 Dec 29, 2024
@openshift-ci-robot
Copy link
Contributor

@mtulio: This pull request references Jira Issue OCPBUGS-46532, which is valid.

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

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.

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws-ccm,periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws

@openshift-ci-robot
Copy link
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

@mtulio: job(s): periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws-ccm,periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws either don't exist or were not found to be affected, and cannot be rehearsed

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws-ccm periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws

@openshift-ci-robot
Copy link
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

@mtulio: job(s): periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws either don't exist or were not found to be affected, and cannot be rehearsed

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024 •
edited
Loading

Flake on KAPI and CLI missing retries:
/pj-rehearse periodic-ci-redhat-openshift-ecosystem-opct-main-4.18-platform-none-vsphere

@openshift-ci-robot
Copy link
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

opct-oci-assisted-4-18 is reporting error in assisted automation to create the cluster (UPI-method). cc @adriengentil (would you mind reviewing if it it's an issue?)

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.18-opct-external-aws-ccm

@openshift-ci-robot
Copy link
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.18-opct-external-aws

@openshift-ci-robot
Copy link
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

@mtulio: job(s): periodic-ci-openshift-release-master-nightly-4.18-opct-external-aws either don't exist or were not found to be affected, and cannot be rehearsed

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.17-opct-external-aws-ccm

@openshift-ci-robot
Copy link
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@mtulio
Copy link
Contributor Author

mtulio commented Dec 29, 2024

Jobs in AWS infra are enough to validate this change.

I will remove hold when 4.17 is done.

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Dec 29, 2024
@mtulio
Copy link
Contributor Author

mtulio commented Dec 30, 2024

AWS jobs are enough to validate the change. Rehearsals ACK.
/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 30, 2024
@deepsm007
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Dec 30, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, mtulio

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 Dec 30, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Dec 30, 2024

@mtulio: 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/rehearse/openshift/assisted-test-infra/master/opct-oci-assisted-4-18 5cf41d9 link unknown /pj-rehearse pull-ci-openshift-assisted-test-infra-master-opct-oci-assisted-4-18
ci/rehearse/periodic-ci-redhat-openshift-ecosystem-opct-main-4.17-platform-external-vsphere-upgrade 5cf41d9 link unknown /pj-rehearse periodic-ci-redhat-openshift-ecosystem-opct-main-4.17-platform-external-vsphere-upgrade
ci/rehearse/periodic-ci-redhat-openshift-ecosystem-opct-main-4.14-platform-none-vsphere-upgrade 5cf41d9 link unknown /pj-rehearse periodic-ci-redhat-openshift-ecosystem-opct-main-4.14-platform-none-vsphere-upgrade
ci/rehearse/periodic-ci-redhat-openshift-ecosystem-opct-main-4.18-platform-none-vsphere 5cf41d9 link unknown /pj-rehearse periodic-ci-redhat-openshift-ecosystem-opct-main-4.18-platform-none-vsphere

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 2a5b38c into openshift:master Dec 30, 2024
14 of 18 checks passed
@openshift-ci-robot
Copy link
Contributor

@mtulio: Jira Issue OCPBUGS-46532: All pull requests linked via external trackers have merged:

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

In response to this:

Bump OPCT for bug fixes.
Ref:

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.

@mtulio mtulio deleted the OCPBUGS-46532 branch December 30, 2024 14:11
Phaow pushed a commit to Phaow/release that referenced this pull request Jan 10, 2025
@mtulio @Phaow
OCPBUGS-46532: bump OPCT to v0.5.1 (openshift#60205)
d2328c1
krishvoor pushed a commit to krishvoor/release that referenced this pull request Jan 29, 2025
@mtulio @krishvoor
OCPBUGS-46532: bump OPCT to v0.5.1 (openshift#60205)
3faca80
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bear-redhat bear-redhat Awaiting requested review from bear-redhat

@deepsm007 deepsm007 Awaiting requested review from deepsm007

Assignees

@adriengentil adriengentil

@deepsm007 deepsm007

@rvanderp3 rvanderp3

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@mtulio @openshift-ci-robot @deepsm007 @adriengentil @rvanderp3