Skip to content

Conversation

varshab1210
Copy link
Member

What type of PR is this?

Uncomment only one /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind bug
/kind cleanup
/kind failing-test
/kind enhancement
/kind documentation
/kind code-refactoring

What does this PR do / why we need it:

Have you updated the necessary documentation?

  • Documentation update is required by this PR.
  • Documentation has been updated.

Which issue(s) this PR fixes:

Fixes #?

Test acceptance criteria:

  • Unit Test
  • E2E Test

How to test changes / Special notes to the reviewer:

Copy link

openshift-ci bot commented Sep 10, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link

openshift-ci bot commented Sep 10, 2025

[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 jopit for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

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

@varshab1210
Copy link
Member Author

/test v4.17-kuttl-sequential
/test v4.17-kuttl-parallel

Copy link

openshift-ci bot commented Sep 16, 2025

@varshab1210: 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/v4.17-kuttl-parallel 3649c9d link true /test v4.17-kuttl-parallel
ci/prow/v4.17-kuttl-sequential 3649c9d link true /test v4.17-kuttl-sequential
ci/prow/v4.19-kuttl-parallel 3649c9d link true /test v4.19-kuttl-parallel
ci/prow/v4.19-kuttl-sequential 3649c9d link true /test v4.19-kuttl-sequential

Full PR test history. Your PR dashboard.

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.

Signed-off-by: Varsha B <[email protected]>
Signed-off-by: Varsha B <[email protected]>
Signed-off-by: Varsha B <[email protected]>
@varshab1210 varshab1210 force-pushed the update-installation-ns-ginkgo branch from 3649c9d to fa12ac7 Compare October 14, 2025 12:30
@varshab1210
Copy link
Member Author

/test v4.17-kuttl-sequential

Copy link

openshift-ci bot commented Oct 14, 2025

@varshab1210: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test unit
/test v4.14-ci-index-gitops-operator-bundle
/test v4.14-e2e
/test v4.14-images
/test v4.14-kuttl-parallel
/test v4.14-kuttl-sequential
/test v4.19-ci-index-gitops-operator-bundle
/test v4.19-e2e
/test v4.19-images
/test v4.19-kuttl-parallel
/test v4.19-kuttl-sequential

Use /test all to run all jobs.

In response to this:

/test v4.17-kuttl-sequential

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.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant