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

OCPERT-49 Add 4.19 auto-release jobs #61397

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

OCPERT-49 Add 4.19 auto-release jobs #61397

wants to merge 3 commits into from
+1,313 −0

Conversation

jhuttana
Copy link
Contributor

@jhuttana jhuttana commented Feb 7, 2025

JIRA issue: https://issues.redhat.com/browse/OCPERT-49
@rioliu-rh Could you please review the changes?

@openshift-ci openshift-ci bot requested review from Phaow and Xia-Zhao-rh February 7, 2025 15:23
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhuttana

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 Feb 7, 2025
@jhuttana
Copy link
Contributor Author

jhuttana commented Feb 7, 2025

/uncc @Phaow
/uncc @Xia-Zhao-rh

@jhuttana
Copy link
Contributor Author

jhuttana commented Feb 7, 2025

/cc @ming1013
/cc @tomasdavidorg
/cc @LuboTerifaj

@jhuttana
Copy link
Contributor Author

jhuttana commented Feb 7, 2025

/cc @rioliu-rh

@openshift-ci openshift-ci bot requested a review from rioliu-rh February 7, 2025 15:26
@jhuttana
Copy link
Contributor Author

jhuttana commented Feb 7, 2025

Still I need to open dependent PRs both in this repo and in https://github.com/openshift/release-tests. So expect few failures yet.

@jhuttana
Copy link
Contributor Author

jhuttana commented Feb 7, 2025

/test ordered-prow-config

@jhuttana jhuttana force-pushed the add_4.19_autorelease_jobs branch from 0a9aa91 to 7472a43 Compare February 7, 2025 17:54
@rioliu-rh
Copy link
Contributor

lgtm, let's trigger rehearsal jobs to verify if the job works as expected.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 8, 2025
@rioliu-rh
Copy link
Contributor

@jhuttana need to rebase

@jhuttana jhuttana force-pushed the add_4.19_autorelease_jobs branch from 7472a43 to 15f8e32 Compare February 9, 2025 14:29
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 9, 2025
@jhuttana
Copy link
Contributor Author

jhuttana commented Feb 9, 2025

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-stable-4.19-upgrade-from-stable-4.18-azure-ipi-fips-f999

@openshift-ci-robot
Copy link
Contributor

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

@jhuttana
Copy link
Contributor Author

jhuttana commented Feb 9, 2025

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-stable-4.19-upgrade-from-stable-4.19-gcp-ipi-f999

@openshift-ci-robot
Copy link
Contributor

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

@jhuttana
Copy link
Contributor Author

jhuttana commented Feb 9, 2025

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-aws-ipi-f999

@openshift-ci-robot
Copy link
Contributor

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

rioliu-rh
rioliu-rh reviewed Feb 10, 2025
View reviewed changes
...hift-tests-private-release-4.19__automated-release-stable-4.19-upgrade-from-stable-4.18.yaml
version_bounds:
lower: 4.18.0-0
upper: 4.19.0-0
target:
Copy link
Contributor

Choose a reason for hiding this comment

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

@jhuttana 4.19 is not GA yet. it does not have build in release stream 4-stable. we only can use ec build instead.

  target:
    release:
      architecture: amd64
      channel: candidate
      version: "4.19"

Copy link
Contributor

Choose a reason for hiding this comment

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

xref: https://github.com/openshift/release/blob/master/ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.19__amd64-stable-4.19-upgrade-from-stable-4.18.yaml#L48-L52

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

Copy link
Contributor

Choose a reason for hiding this comment

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

the update is incorrect. the expected content is mentioned above

rioliu-rh
rioliu-rh reviewed Feb 10, 2025
View reviewed changes
...hift-tests-private-release-4.19__automated-release-stable-4.19-upgrade-from-stable-4.19.yaml
releases:
latest:
prerelease:
architecture: amd64
Copy link
Contributor

Choose a reason for hiding this comment

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

same concern

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@jhuttana
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-stable-4.19-upgrade-from-stable-4.18-azure-ipi-fips-f999

@openshift-ci-robot
Copy link
Contributor

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

@openshift-ci-robot
Copy link
Contributor

@jhuttana, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: configuration has 2 errors:

 * releases.latest.product: must be one of ocp, okd, okd-scos
 * releases.target.product: must be one of ocp, okd, okd-scos
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.

@jhuttana
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-stable-4.19-upgrade-from-stable-4.19-gcp-ipi-f999

@openshift-ci-robot
Copy link
Contributor

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

@openshift-ci-robot
Copy link
Contributor

@jhuttana, pj-rehearse: unable to determine affected jobs ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: configuration has 2 errors:

 * releases.latest.product: must be one of ocp, okd, okd-scos
 * releases.target.product: must be one of ocp, okd, okd-scos

If the problem persists, please contact Test Platform.

1 similar comment
@openshift-ci-robot
Copy link
Contributor

@jhuttana, pj-rehearse: unable to determine affected jobs ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: configuration has 2 errors:

 * releases.latest.product: must be one of ocp, okd, okd-scos
 * releases.target.product: must be one of ocp, okd, okd-scos

If the problem persists, please contact Test Platform.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 10, 2025

@jhuttana: 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/openshift-image-mirror-mappings 30c6c29 link true /test openshift-image-mirror-mappings
ci/prow/ci-operator-config 30c6c29 link true /test ci-operator-config
ci/prow/ci-operator-registry 30c6c29 link true /test ci-operator-registry
ci/rehearse/periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-aws-ipi-f999 15f8e32 link unknown /pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-aws-ipi-f999
ci/rehearse/periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-stable-4.19-upgrade-from-stable-4.18-azure-ipi-fips-f999 15f8e32 link unknown /pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-stable-4.19-upgrade-from-stable-4.18-azure-ipi-fips-f999
ci/prow/generated-config 30c6c29 link true /test generated-config
ci/prow/check-gh-automation 30c6c29 link true /test check-gh-automation
ci/prow/ci-operator-config-metadata 30c6c29 link true /test ci-operator-config-metadata
ci/rehearse/periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-stable-4.19-upgrade-from-stable-4.19-gcp-ipi-f999 15f8e32 link unknown /pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-stable-4.19-upgrade-from-stable-4.19-gcp-ipi-f999

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.

@jhuttana
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-automated-release-stable-4.19-upgrade-from-stable-4.18-azure-ipi-fips-f999

@openshift-ci-robot
Copy link
Contributor

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

@openshift-ci-robot
Copy link
Contributor

@jhuttana, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: configuration has 2 errors:

 * releases.latest.product: must be one of ocp, okd, okd-scos
 * releases.target.product: must be one of ocp, okd, okd-scos
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.

@openshift-ci-robot
Copy link
Contributor

@jhuttana, pj-rehearse: unable to determine affected jobs ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: configuration has 2 errors:

 * releases.latest.product: must be one of ocp, okd, okd-scos
 * releases.target.product: must be one of ocp, okd, okd-scos

If the problem persists, please contact Test Platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rioliu-rh rioliu-rh rioliu-rh left review comments

@LuboTerifaj LuboTerifaj Awaiting requested review from LuboTerifaj

@ming1013 ming1013 Awaiting requested review from ming1013

@tomasdavidorg tomasdavidorg Awaiting requested review from tomasdavidorg

Assignees
No one assigned
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@jhuttana @rioliu-rh @openshift-ci-robot @openshift-merge-robot