Skip to content

USHIFT-4121 USHIFT-4123: Skip sig-ci tests, revert ovnk image#3837

Merged
openshift-merge-bot[bot] merged 2 commits into
openshift:mainfrom
pacevedom:skip-fips-job-name-test
Sep 1, 2024
Merged

USHIFT-4121 USHIFT-4123: Skip sig-ci tests, revert ovnk image#3837
openshift-merge-bot[bot] merged 2 commits into
openshift:mainfrom
pacevedom:skip-fips-job-name-test

Conversation

@pacevedom

Copy link
Copy Markdown
Contributor

Which issue(s) this PR addresses:

Closes #

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 30, 2024
@openshift-ci

openshift-ci Bot commented Aug 30, 2024

Copy link
Copy Markdown
Contributor

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 30, 2024
@pacevedom

Copy link
Copy Markdown
Contributor Author

/test ocp-full-conformance-rhel-eus

2 similar comments
@pacevedom

Copy link
Copy Markdown
Contributor Author

/test ocp-full-conformance-rhel-eus

@pacevedom

Copy link
Copy Markdown
Contributor Author

/test ocp-full-conformance-rhel-eus

@pacevedom pacevedom force-pushed the skip-fips-job-name-test branch from 964d573 to 9becf35 Compare August 31, 2024 22:51
@pacevedom pacevedom changed the title wip: do not merge USHIFT-4121 USHIFT-4123: Skip sig-ci tests, revert ovnk image Aug 31, 2024
@openshift-ci-robot

openshift-ci-robot commented Aug 31, 2024

Copy link
Copy Markdown

@pacevedom: This pull request references USHIFT-4121 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.

This pull request references USHIFT-4123 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

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-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 31, 2024
@pacevedom pacevedom marked this pull request as ready for review August 31, 2024 22:51
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 31, 2024
@openshift-ci openshift-ci Bot requested review from ggiguash and pmtk August 31, 2024 22:52
@pacevedom

Copy link
Copy Markdown
Contributor Author

/test test-rebase

1 similar comment
@pacevedom

Copy link
Copy Markdown
Contributor Author

/test test-rebase

@openshift-ci

openshift-ci Bot commented Sep 1, 2024

Copy link
Copy Markdown
Contributor

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

@ggiguash

ggiguash commented Sep 1, 2024

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 1, 2024
@openshift-ci

openshift-ci Bot commented Sep 1, 2024

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom

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:

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

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants