Skip to content

DPTP-4387: Update BASE_DOMAIN and rebalance jobs #63820

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

Merged
merged 4 commits into from
Apr 15, 2025

Conversation

deepsm007
Copy link
Contributor

@deepsm007 deepsm007 commented Apr 14, 2025

Remove the hard coded BaseDomain, update the vault secrets and rotate the new token, rebalance jobs between multiple accounts

release profile balance -C "$RELEASE_REPO" --from=aws --scaling-factor=0.5 --to=aws-2 --balancing-factors=1 --exclude-orgs=openshift-priv

targeted tests: 8061
tests to balance: 4030
profiles:
aws-2: 4030

/cc @openshift/test-platform

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 14, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 14, 2025

@deepsm007: This pull request references DPTP-4387 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

Remove the hard coded BaseDomain, update the vault secrets and rotate the new token, rebalance jobs between multiple accounts

/cc @openshift/test-platform

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 openshift-ci bot requested a review from a team April 14, 2025 18:14
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 14, 2025
Copy link
Contributor

openshift-ci bot commented Apr 14, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@deepsm007
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@deepsm007: 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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 14, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 14, 2025

@deepsm007: This pull request references DPTP-4387 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

Remove the hard coded BaseDomain, update the vault secrets and rotate the new token, rebalance jobs between multiple accounts

release profile balance -C "$RELEASE_REPO" --from=aws --scaling-factor=0.5 --to=aws-2 --balancing-factors=1 --exclude-orgs=openshift-priv

/cc @openshift/test-platform

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

openshift-ci-robot commented Apr 14, 2025

@deepsm007: This pull request references DPTP-4387 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

Remove the hard coded BaseDomain, update the vault secrets and rotate the new token, rebalance jobs between multiple accounts

release profile balance -C "$RELEASE_REPO" --from=aws --scaling-factor=0.5 --to=aws-2 --balancing-factors=1 --exclude-orgs=openshift-priv

targeted tests: 8061
tests to balance: 4030
profiles:
aws-2: 4030

/cc @openshift/test-platform

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

openshift-ci-robot commented Apr 14, 2025

@deepsm007: This pull request references DPTP-4387 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

Remove the hard coded BaseDomain, update the vault secrets and rotate the new token, rebalance jobs between multiple accounts

release profile balance -C "$RELEASE_REPO" --from=aws --scaling-factor=0.5 --to=aws-2 --balancing-factors=1 --exclude-orgs=openshift-priv

targeted tests: 8061
tests to balance: 4030
profiles:
aws-2: 4030

/cc @openshift/test-platform

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.

@deepsm007
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-csi periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-etcd-scaling

@openshift-ci-robot
Copy link
Contributor

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

@deepsm007 deepsm007 marked this pull request as ready for review April 14, 2025 18:29
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 14, 2025
@deepsm007
Copy link
Contributor Author

/hold

@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 Apr 14, 2025
@hector-vido
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 14, 2025
Copy link
Contributor

@bear-redhat bear-redhat left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 14, 2025
@deepsm007
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-csi periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-etcd-scaling

@openshift-ci-robot
Copy link
Contributor

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

@deepsm007
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

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

@deepsm007
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-csi

@openshift-ci-robot
Copy link
Contributor

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

@deepsm007
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-csi periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-etcd-scaling

@openshift-ci-robot
Copy link
Contributor

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

@deepsm007
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-csi

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@deepsm007: 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-monitoring-plugin-release-4.20-e2e-aws-ovn-upgrade openshift/monitoring-plugin presubmit Ci-operator config changed
pull-ci-openshift-monitoring-plugin-main-e2e-aws-ovn-upgrade openshift/monitoring-plugin presubmit Ci-operator config changed
pull-ci-openshift-monitoring-plugin-main-okd-scos-e2e-aws-ovn openshift/monitoring-plugin presubmit Ci-operator config changed
pull-ci-openshift-monitoring-plugin-release-4.18-okd-scos-e2e-aws-ovn openshift/monitoring-plugin presubmit Ci-operator config changed
pull-ci-openshift-monitoring-plugin-main-e2e-aws-ovn openshift/monitoring-plugin presubmit Registry content changed
pull-ci-openshift-monitoring-plugin-release-4.20-e2e-aws-ovn openshift/monitoring-plugin presubmit Registry content changed
pull-ci-openshift-monitoring-plugin-release-4.19-e2e-aws-ovn openshift/monitoring-plugin presubmit Registry content changed
pull-ci-openshift-monitoring-plugin-release-4.18-e2e-aws-ovn openshift/monitoring-plugin presubmit Registry content changed
pull-ci-openshift-monitoring-plugin-release-4.19-e2e-aws-ovn-upgrade openshift/monitoring-plugin presubmit Registry content changed
pull-ci-openshift-monitoring-plugin-release-4.18-e2e-aws-ovn-upgrade openshift/monitoring-plugin presubmit Registry content changed
pull-ci-openshift-oc-compliance-master-e2e openshift/oc-compliance presubmit Ci-operator config changed
pull-ci-kubevirt-ui-kubevirt-plugin-main-kubevirt-e2e-aws kubevirt-ui/kubevirt-plugin presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.17-ci-install-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.17-ci-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.17-ci-must-gather-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.16-ci-install-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.16-ci-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.16-ci-must-gather-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.15-ci-install-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.15-ci-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.15-ci-must-gather-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.14-ci-install-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.14-ci-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.14-ci-must-gather-e2e openshift-kni/numaresources-operator presubmit Registry content changed
pull-ci-openshift-kni-numaresources-operator-release-4.13-ci-install-e2e openshift-kni/numaresources-operator presubmit Registry content changed

A total of 13087 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
The following jobs are not rehearsable without the network-access-rehearsals-ok, and approved labels present on this PR. This is due to the restrict_network_access field being set to false. The network-access-rehearsals-ok label can be added by any openshift org member other than the PR's author by commenting: /pj-rehearse network-access-allowed:

Test name
periodic-ci-openshift-microshift-release-4.19-periodics-e2e-aws-tests-cache-nightly-arm
periodic-ci-openshift-microshift-release-4.19-periodics-e2e-aws-tests-cache-nightly
periodic-ci-openshift-microshift-main-e2e-aws-tests-cache-nightly
periodic-ci-openshift-microshift-main-e2e-aws-tests-cache-nightly-arm
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-cache-arm
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-cache
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 list to get an up-to-date list of affected jobs
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.

@deepsm007
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-csi

@openshift-ci-robot
Copy link
Contributor

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

@deepsm007
Copy link
Contributor Author

/pj-rehearse ack
/unhold

@openshift-ci-robot
Copy link
Contributor

@deepsm007: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or 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 Apr 15, 2025
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 15, 2025
@openshift-ci-robot
Copy link
Contributor

@deepsm007: 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 lgtm Indicates that a PR is ready to be merged. label Apr 15, 2025
Copy link
Contributor

openshift-ci bot commented Apr 15, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bear-redhat, deepsm007, hector-vido, liangxia

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 e059874 into openshift:master Apr 15, 2025
15 of 16 checks passed
Copy link
Contributor

openshift-ci bot commented Apr 15, 2025

@deepsm007: 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/stolostron/observatorium-operator/release-2.1/e2e-test 7c1a57e link unknown /pj-rehearse pull-ci-stolostron-observatorium-operator-release-2.1-e2e-test
ci/rehearse/openshift/cluster-openshift-apiserver-operator/release-4.12/e2e-upgrade 7c1a57e link unknown /pj-rehearse pull-ci-openshift-cluster-openshift-apiserver-operator-release-4.12-e2e-upgrade
ci/rehearse/periodic-ci-3scale-qe-3scale-deploy-main-3scale-amp-ocp4.13-lp-interop-3scale-amp-interop-aws 7c1a57e link unknown /pj-rehearse periodic-ci-3scale-qe-3scale-deploy-main-3scale-amp-ocp4.13-lp-interop-3scale-amp-interop-aws
ci/rehearse/openshift/cluster-openshift-apiserver-operator/release-4.12/e2e-aws-ovn 7c1a57e link unknown /pj-rehearse pull-ci-openshift-cluster-openshift-apiserver-operator-release-4.12-e2e-aws-ovn
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-etcd-scaling 918ca41 link unknown /pj-rehearse periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-etcd-scaling

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.

xingxingxia added a commit to xingxingxia/release that referenced this pull request Apr 15, 2025
@openshift-ci-robot
Copy link
Contributor

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

could not load configuration from base revision of release repo: could not checkout worktree: '[git checkout 3da0713fd805b169f32f15235a893d16a7370497]' failed with out:  and error exec: Stdout already set

If the problem persists, please contact Test Platform.

mehabhalodiya pushed a commit to mehabhalodiya/release that referenced this pull request Apr 15, 2025
* Utilize BASE_DOMAIN from cluster-profile

* Remove hard-coded BASE_DOMAIN for aws-2 account

* Rebalance jobs between aws & aws-2 cluster-profiles

* make jobs
mehabhalodiya pushed a commit to mehabhalodiya/release that referenced this pull request Apr 15, 2025
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-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
Development

Successfully merging this pull request may close these issues.

5 participants