[WIP] add Azure/ARO-RP

[stevekuznetsov]

No description provided.

[openshift-ci-robot]

@stevekuznetsov, 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 4 errors:

 * tests[0]: invalid cluster profile "aro-classic-int"
 * tests[1]: invalid cluster profile "aro-classic-stg"
 * tests[2]: invalid cluster profile "aro-classic-prod"
 * tests[3]: invalid cluster profile "aro-classic-dev"

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: stevekuznetsov
Once this PR has been reviewed and has the lgtm label, please assign pruan-rht 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/step-registry/cluster-profiles/OWNERS
• clusters/OWNERS
• core-services/ci-secret-bootstrap/OWNERS

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

[openshift-ci]

Hi @stevekuznetsov. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[deepsm007]

/ok-to-test

[openshift-ci]

@stevekuznetsov: 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/check-gh-automation-tide	962b4c6	link	true	/test check-gh-automation-tide
ci/prow/openshift-image-mirror-mappings	962b4c6	link	true	/test openshift-image-mirror-mappings
ci/prow/ci-operator-registry	962b4c6	link	true	/test ci-operator-registry
ci/prow/ci-operator-config	962b4c6	link	true	/test ci-operator-config
ci/prow/ci-operator-config-metadata	962b4c6	link	true	/test ci-operator-config-metadata
ci/prow/generated-config	962b4c6	link	true	/test generated-config
ci/prow/step-registry-metadata	962b4c6	link	true	/test step-registry-metadata
ci/prow/check-cluster-profiles-config	962b4c6	link	false	/test check-cluster-profiles-config
ci/prow/check-gh-automation	962b4c6	link	true	/test check-gh-automation
ci/prow/owners	962b4c6	link	true	/test owners

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-sigs/prow repository. I understand the commands that are listed here.