Skip to content

Conversation

@yunjiang29
Copy link
Contributor

@yunjiang29 yunjiang29 commented Nov 21, 2022

Background:

there are some options for this fix:

  1. provide instance type in both AMD and ARM job configurations explicitly, and remove default value from the provision chain.
  2. provide instance type in ARM job configurations explicitly, AMD uses the default value in the provision chain.
  3. Same as 2), but reverse ARM and AMD.

I choose 2) in this PR because of the fewer code changes.

@aleskandro @lwan-wanglin @jianlinliu, any comments/ideas on this?

@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 Nov 21, 2022
@openshift-ci-robot
Copy link
Contributor

@yunjiang29: the following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-proxy-cco-manual-security-token-service-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.11-arm64-nightly-aws-ipi-ovn-ipsec-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-4.13-upgrade-from-stable-4.12-aws-ipi-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-aws-ipi-sdn-p1-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-aws-ipi-ovn-ipsec-destructive-p3-f28 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-aws-ipi-proxy-cco-manual-security-token-service-p2-f4 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-aws-ipi-destructive-p3-f28 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-4.12-upgrade-from-stable-4.11-aws-ipi-private-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-sdn-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-proxy-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-aws-ipi-disconnected-private-p1-f4 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-destructive-p3-f28 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-aws-ipi-ovn-ipsec-p1-f4 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-ovn-ipsec-destructive-p3-f28 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-ovn-sdn2ovn-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-disconnected-private-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-ovn-ingress-nlb-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-aws-ipi-ovn-sdn2ovn-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-4.12-upgrade-from-stable-4.11-aws-ipi-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-ovn-ipsec-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-4.13-upgrade-from-stable-4.12-aws-ipi-private-p2-f7 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-aws-ipi-ovn-ingress-nlb-p1-f4 N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-private-p2-f7 N/A periodic Ci-operator config 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 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse refresh to get an updated list of affected jobs (useful if you have new pushes to the branch)

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.

@yunjiang29 yunjiang29 force-pushed the fix-arm-instance-type-issue branch from f431246 to 6956cff Compare November 21, 2022 15:27
@yunjiang29
Copy link
Contributor Author

/unhold

@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 Nov 21, 2022
@aleskandro
Copy link
Member

Hi @yunjiang29 I'm ok with any of the solutions you propose.

It's good enough just to specify the instance types to use (as we do in flexy).

I'd say the 2nd proposal is the less risky to avoid changing too many x86 prow configs.

Instead, having the x86 instance types explicitly called out is a "nice-to-have" for the others that create new profiles: they would see very similar configs in both the architectures' prow configs.

@yunjiang29
Copy link
Contributor Author

@aleskandro thanks for your feedback.

@yunjiang29
Copy link
Contributor Author

/pj-rehearse

@lwan-wanglin
Copy link
Contributor

lwan-wanglin commented Nov 22, 2022

Does this influnce dev's jobs? they use cluster_profile: aws-arm64 to represent arm clusters, do we need to explicitly set instance for dev's profiles too?

@jianlinliu
Copy link
Contributor

Does this influnce dev's jobs? they use cluster_profile: aws-arm64 to represent arm clusters, do we need to explicitly set instance for dev's profiles too?

I guess no, if nothing set for CONTROL_PLANE_INSTANCE_TYPE and COMPUTE_NODE_TYPE, the same logic as before.

@yunjiang29
Copy link
Contributor Author

Does this influnce dev's jobs? they use cluster_profile: aws-arm64 to represent arm clusters, do we need to explicitly set instance for dev's profiles too?

I guess no, if nothing set for CONTROL_PLANE_INSTANCE_TYPE and COMPUTE_NODE_TYPE, the same logic as before.

Correct. The types are added in job config level, which is for QE only.

@yunjiang29
Copy link
Contributor Author

Some jobs' installation get passed, the change works.
/pj-rehearse ack

@kuiwang02 can you approve this PR? thanks.

@kuiwang02
Copy link
Contributor

Some jobs' installation get passed, the change works. /pj-rehearse ack

@kuiwang02 can you approve this PR? thanks.

please request qe-productivity team to approve it.
@liangxia @jhou1 please check it. thanks.

@liangxia
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 22, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liangxia, yunjiang29

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Nov 22, 2022
@yunjiang29
Copy link
Contributor Author

/pj-rehearse ack

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Nov 22, 2022
@openshift-merge-robot openshift-merge-robot merged commit a9726ad into openshift:master Nov 22, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2022

@yunjiang29: Updated the following 3 configmaps:

  • ci-operator-4.11-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-openshift-tests-private-release-4.11__arm64-nightly.yaml using file ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.11__arm64-nightly.yaml
  • ci-operator-4.12-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-openshift-tests-private-release-4.12__arm64-nightly-4.12-upgrade-from-stable-4.11.yaml using file ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.12__arm64-nightly-4.12-upgrade-from-stable-4.11.yaml
    • key openshift-openshift-tests-private-release-4.12__arm64-nightly.yaml using file ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.12__arm64-nightly.yaml
  • ci-operator-4.13-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-openshift-tests-private-release-4.13__arm64-nightly-4.13-upgrade-from-stable-4.12.yaml using file ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.13__arm64-nightly-4.13-upgrade-from-stable-4.12.yaml
    • key openshift-openshift-tests-private-release-4.13__arm64-nightly.yaml using file ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.13__arm64-nightly.yaml
Details

In response to this:

Background:

there are some options for this fix:

  1. provide instance type in both AMD and ARM job configurations explicitly, and remove default value from the provision chain.
  2. provide instance type in ARM job configurations explicitly, AMD uses the default value in the provision chain.
  3. Same as 2), but reverse ARM and AMD.

I choose 2) in this PR because of the fewer code changes.

@aleskandro @lwan-wanglin @jianlinliu, any comments/ideas on 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 kubernetes/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2022

@yunjiang29: 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/periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-4.13-upgrade-from-stable-4.12-aws-ipi-p2-f7 6956cff link unknown /pj-rehearse
ci/rehearse/periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-nightly-aws-ipi-destructive-p3-f28 6956cff link unknown /pj-rehearse

Full PR test history. Your PR dashboard.

Details

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.

@yunjiang29 yunjiang29 deleted the fix-arm-instance-type-issue branch July 21, 2023 08:58
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. 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.

8 participants