Skip to content

Conversation

pavolloffay
Copy link
Member

Version(s):

OCP 4.12-4.19

RHOSDT 3.6

Issue:

https://issues.redhat.com/browse/TRACING-5120

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Signed-off-by: Pavol Loffay <p.loffay@gmail.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 28, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 28, 2025

@pavolloffay: This pull request references TRACING-5120 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.19.0" version, but no target version was set.

In response to this:

Version(s):

OCP 4.12-4.19

RHOSDT 3.6

Issue:

https://issues.redhat.com/browse/TRACING-5120

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 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 Feb 28, 2025
Copy link

openshift-ci bot commented Feb 28, 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

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 28, 2025
@pavolloffay
Copy link
Member Author

/test all

@ocpdocs-previewbot
Copy link

Copy link

openshift-ci bot commented Feb 28, 2025

@pavolloffay: all tests passed!

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.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 30, 2025
@max-cx
Copy link
Contributor

max-cx commented Jun 15, 2025

@pavolloffay, feel free to close this PR because I opened #94800.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants