Skip to content

Conversation

@Thealisyed
Copy link

…space in spec.path

openshift/library-go#2012 was already merged
hence we ran the following commands for this PR:
go get github.com/openshift/library-go@2dd58ebcfe22424a4e7ae919ab61e62a0d03632c go mod tidy

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Nov 11, 2025
@openshift-ci-robot
Copy link

@Thealisyed: This pull request references Jira Issue OCPBUGS-61662, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-47773 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-47773 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0, 4.20.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

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

Details

In response to this:

…space in spec.path

openshift/library-go#2012 was already merged
hence we ran the following commands for this PR:
go get github.com/openshift/library-go@2dd58ebcfe22424a4e7ae919ab61e62a0d03632c go mod tidy

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
Copy link
Contributor

openshift-ci bot commented Nov 11, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@coderabbitai
Copy link

coderabbitai bot commented Nov 11, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Comment @coderabbitai help to get the list of available commands and usage tips.

…space in spec.path

openshift/library-go#2012 was already merged
hence we ran the following commands for this PR:
go get github.com/openshift/library-go@2dd58ebcfe22424a4e7ae919ab61e62a0d03632c
go mod tidy
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 13, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 4, 2025

@Thealisyed: 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/e2e-aws-ovn 3753567 link true /test e2e-aws-ovn
ci/prow/images 3753567 link true /test images
ci/prow/verify 3753567 link true /test verify
ci/prow/okd-scos-e2e-aws-ovn 3753567 link false /test okd-scos-e2e-aws-ovn
ci/prow/unit 3753567 link true /test unit
ci/prow/okd-scos-images 3753567 link true /test okd-scos-images
ci/prow/e2e-aws-ovn-serial-2of2 3753567 link true /test e2e-aws-ovn-serial-2of2
ci/prow/e2e-aws-ovn-serial-1of2 3753567 link true /test e2e-aws-ovn-serial-1of2
ci/prow/e2e-aws-ovn-upgrade 3753567 link true /test e2e-aws-ovn-upgrade
ci/prow/go-verify-deps 3753567 link true /test go-verify-deps

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.

@Thealisyed Thealisyed closed this Dec 18, 2025
@openshift-ci-robot
Copy link

@Thealisyed: This pull request references Jira Issue OCPBUGS-61662. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

…space in spec.path

openshift/library-go#2012 was already merged
hence we ran the following commands for this PR:
go get github.com/openshift/library-go@2dd58ebcfe22424a4e7ae919ab61e62a0d03632c go mod tidy

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.

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

Labels

jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants