Add vsphere-approvers to all the steps

[jcpowermac]

No description provided.

[openshift-ci]

@jcpowermac: 1 invalid OWNERS file

Details

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

[openshift-ci]

Cannot parse file: error converting YAML to JSON: yaml: line 5: did not find expected key.

[jcpowermac]

/assign @anuragthehatter @patrickdillon

[vr4manta]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jcpowermac, vr4manta
Once this PR has been reviewed and has the lgtm label, please ask for approval from anuragthehatter, patrickdillon. 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/cucushift/installer/rehearse/vsphere/ipi/ovn/OWNERS
• ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/sdn/OWNERS
• ci-operator/step-registry/cucushift/installer/rehearse/vsphere/upi/disconnected/sdn/OWNERS
• ci-operator/step-registry/ipi/conf/vsphere/OWNERS [jcpowermac,vr4manta]
• ci-operator/step-registry/ipi/vsphere/proxy/OWNERS [jcpowermac,vr4manta]
• ci-operator/step-registry/upi/deprovision/vsphere/workers-rhel/OWNERS [jcpowermac,vr4manta]
• ci-operator/step-registry/vsphere/OWNERS [jcpowermac,vr4manta]
• ci-operator/step-registry/workers-rhel/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]

New changes are detected. LGTM label has been removed.

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@jcpowermac: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

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]

@jcpowermac: all tests passed!

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.