Skip to content

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

Open
winiciusallan wants to merge 1 commit into
openshift:mainfrom
shiftstack:servergroup-without-ns
Open

OCPBUGS-98468: Create oc CLI without namespace in servergroup spec#283
winiciusallan wants to merge 1 commit into
openshift:mainfrom
shiftstack:servergroup-without-ns

Conversation

@winiciusallan

Copy link
Copy Markdown
Member

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 11, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@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-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jul 11, 2026
@openshift-ci openshift-ci Bot requested review from eshulman2 and mandre July 11, 2026 20:09
@openshift-ci

openshift-ci Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mandre 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:

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 commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants