OCPBUGS-98468: Create oc CLI without namespace in servergroup spec

[winiciusallan]

Some jobs have been failing with the following message

project.project.openshift.io "e2e-test-openstack-<id>" already exists

This PR is an attempt to avoid that two concurrent ginkgo creates projects at the same time, leading to the same project name and therefore a test failure

[openshift-ci-robot]

@winiciusallan: This pull request references Jira Issue OCPBUGS-98468, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Some jobs have been failing with the following message

project.project.openshift.io "e2e-test-openstack-<id>" already exists

This PR is an attempt to avoid that two concurrent ginkgo creates projects at the same time, leading to the same project name and therefore a test failure

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]

@winiciusallan: 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.

[mandre]

At least, this is not breaking the job.
/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mandre

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:

• OWNERS [mandre]

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

[mandre]

/jira backport release-4.22,release-4.21,release-4.20,release-4.19,release-4.18

[mandre]

/verified by CI

[openshift-ci-robot]

@mandre: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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]

@winiciusallan: Jira Issue Verification Checks: Jira Issue OCPBUGS-98468
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-98468 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Some jobs have been failing with the following message

project.project.openshift.io "e2e-test-openstack-<id>" already exists

This PR is an attempt to avoid that two concurrent ginkgo creates projects at the same time, leading to the same project name and therefore a test failure

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]

@mandre: The following backport issues have been created:

• Jira Issue OCPBUGS-98477 for branch release-4.22
• Jira Issue OCPBUGS-98478 for branch release-4.21
• Jira Issue OCPBUGS-98479 for branch release-4.20
• Jira Issue OCPBUGS-98480 for branch release-4.19
• Jira Issue OCPBUGS-98481 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18

Details

In response to this:

/jira backport release-4.22,release-4.21,release-4.20,release-4.19,release-4.18

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-cherrypick-robot]

@openshift-ci-robot: new pull request created: #284

Details

In response to this:

@mandre: The following backport issues have been created:

• Jira Issue OCPBUGS-98477 for branch release-4.22
• Jira Issue OCPBUGS-98478 for branch release-4.21
• Jira Issue OCPBUGS-98479 for branch release-4.20
• Jira Issue OCPBUGS-98480 for branch release-4.19
• Jira Issue OCPBUGS-98481 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18

In response to this:

/jira backport release-4.22,release-4.21,release-4.20,release-4.19,release-4.18

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.

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-cherrypick-robot]

@openshift-ci-robot: new pull request created: #285

Details

In response to this:

@mandre: The following backport issues have been created:

• Jira Issue OCPBUGS-98477 for branch release-4.22
• Jira Issue OCPBUGS-98478 for branch release-4.21
• Jira Issue OCPBUGS-98479 for branch release-4.20
• Jira Issue OCPBUGS-98480 for branch release-4.19
• Jira Issue OCPBUGS-98481 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18

In response to this:

/jira backport release-4.22,release-4.21,release-4.20,release-4.19,release-4.18

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.

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-cherrypick-robot]

@openshift-ci-robot: new pull request created: #286

Details

In response to this:

@mandre: The following backport issues have been created:

• Jira Issue OCPBUGS-98477 for branch release-4.22
• Jira Issue OCPBUGS-98478 for branch release-4.21
• Jira Issue OCPBUGS-98479 for branch release-4.20
• Jira Issue OCPBUGS-98480 for branch release-4.19
• Jira Issue OCPBUGS-98481 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18

In response to this:

/jira backport release-4.22,release-4.21,release-4.20,release-4.19,release-4.18

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.

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-cherrypick-robot]

@openshift-ci-robot: new pull request created: #287

Details

In response to this:

@mandre: The following backport issues have been created:

• Jira Issue OCPBUGS-98477 for branch release-4.22
• Jira Issue OCPBUGS-98478 for branch release-4.21
• Jira Issue OCPBUGS-98479 for branch release-4.20
• Jira Issue OCPBUGS-98480 for branch release-4.19
• Jira Issue OCPBUGS-98481 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18

In response to this:

/jira backport release-4.22,release-4.21,release-4.20,release-4.19,release-4.18

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.

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-cherrypick-robot]

@openshift-ci-robot: new pull request created: #288

Details

In response to this:

@mandre: The following backport issues have been created:

• Jira Issue OCPBUGS-98477 for branch release-4.22
• Jira Issue OCPBUGS-98478 for branch release-4.21
• Jira Issue OCPBUGS-98479 for branch release-4.20
• Jira Issue OCPBUGS-98480 for branch release-4.19
• Jira Issue OCPBUGS-98481 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18

In response to this:

/jira backport release-4.22,release-4.21,release-4.20,release-4.19,release-4.18

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.

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.