WIP: OCPQE-31577: filter out GCP AI zones, along with dealing with cutom machine types

[jianli-wei]

• merge step ipi-conf-gcp-control-plane-node-type into step ipi-conf-gcp
• append step ipi-conf-gcp-zones to chain ipi-conf-gcp
• update step ipi-conf-gcp-zone, to support one new env var EXCLUDE_ZONES_PATTERN, default empty, and when set, zones matching the pattern will be excluded, and then zones will be set according to either explicit env vars of control-plane & compute/worker nodes types, or from install-config.yaml controlPlane.platform.gcp.type / compute[0].platform.gcp.type / platform.gcp.defaultMachinePlatform.type
• update step ipi-conf-gcp, to remove the changes introduced by Filter out AI zones for standard machine types and randomize zone selection #74093

[openshift-ci-robot]

@jianli-wei: This pull request references OCPQE-31577 which is a valid jira issue.

Details

In response to this:

WIP

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]

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

could not determine changed registry steps: could not load step registry: [chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones, workflow/cucushift-installer-rehearse-gcp-ipi-c3-metal-private: chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones]

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.

[openshift-ci-robot]

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

could not determine changed registry steps: could not load step registry: [chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones, workflow/cucushift-installer-rehearse-gcp-ipi-c3-metal-private: chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones]

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.

[openshift-ci-robot]

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

could not determine changed registry steps: could not load step registry: [chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones, workflow/cucushift-installer-rehearse-gcp-ipi-c3-metal-private: chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones]

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jianli-wei
Once this PR has been reviewed and has the lgtm label, please assign csams, jhuttana, jianlinliu, joelspeed for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• ci-operator/config/opendatahub-io/opendatahub-operator/OWNERS
• ci-operator/config/openshift/openshift-tests-private/OWNERS
• ci-operator/step-registry/cucushift/installer/rehearse/gcp/OWNERS [jianli-wei]
• ci-operator/step-registry/ipi/conf/gcp/OWNERS
• ci-operator/step-registry/openshift/e2e/gcp/capi/OWNERS
• ci-operator/step-registry/openshift/e2e/gcp/ccm/OWNERS
• ci-operator/step-registry/openshift/e2e/gcp/custom-dns/OWNERS [jianli-wei]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

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

could not determine changed registry steps: could not load step registry: [chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones, workflow/cucushift-installer-rehearse-gcp-ipi-c3-metal-private: chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones]

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.

[openshift-ci-robot]

@jianli-wei: This pull request references OCPQE-31577 which is a valid jira issue.

Details

In response to this:

• merge step ipi-conf-gcp-control-plane-node-type into step ipi-conf-gcp
• append step ipi-conf-gcp-zones to chain ipi-conf-gcp
• update step ipi-conf-gcp-zone, to support one new env var EXCLUDE_ZONES_PATTERN, default empty, and when set, zones matching the pattern will be excluded, and then zones will be set according to either explicit env vars of control-plane & compute/worker nodes types, or from install-config.yaml controlPlane.platform.gcp.type / compute[0].platform.gcp.type / platform.gcp.defaultMachinePlatform.type

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]

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

could not determine changed registry steps: could not load step registry: [chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones, workflow/cucushift-installer-rehearse-gcp-ipi-c3-metal-private: chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones]

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.

[openshift-ci-robot]

@jianli-wei: This pull request references OCPQE-31577 which is a valid jira issue.

Details

In response to this:

• merge step ipi-conf-gcp-control-plane-node-type into step ipi-conf-gcp
• append step ipi-conf-gcp-zones to chain ipi-conf-gcp
• update step ipi-conf-gcp-zone, to support one new env var EXCLUDE_ZONES_PATTERN, default empty, and when set, zones matching the pattern will be excluded, and then zones will be set according to either explicit env vars of control-plane & compute/worker nodes types, or from install-config.yaml controlPlane.platform.gcp.type / compute[0].platform.gcp.type / platform.gcp.defaultMachinePlatform.type
• update step ipi-conf-gcp, to remove the changes introduced by Filter out AI zones for standard machine types and randomize zone selection #74093

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]

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

could not determine changed registry steps: could not load step registry: [chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones, workflow/cucushift-installer-rehearse-gcp-ipi-c3-metal-private: chain/cucushift-installer-rehearse-gcp-ipi-c3-metal-private-provision: duplicate name: ipi-conf-gcp-zones]

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.