Skip to content

Conversation

@vparfonov
Copy link
Contributor

Description

/cc @jcantrill
/assign @jcantrill

Links

@vparfonov
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 24, 2025
@openshift-ci openshift-ci bot requested review from Clee2691 and jcantrill October 24, 2025 13:01
@anpingli
Copy link

anpingli commented Oct 24, 2025

@vparfonov the collector raise message below when test using this PR.

oc logs collector-b5vvj
Creating the directory used for persisting Vector state /var/lib/vector/openshift-logging/collector
Starting Vector process...
2025-10-24T15:33:24.972170Z ERROR vector::cli: Configuration error. error=Input "output_my_lokistack_route.audit" for transform "output_my_lokistack_audit_remap" doesn't match any components.
2025-10-24T15:33:24.972195Z ERROR vector::cli: Configuration error. error=Input "output_my_lokistack_route.infrastructure" for transform "output_my_lokistack_infrastructure_remap" doesn't match any components.

The vector.toml https://privatebin.corp.redhat.com/?7c92963298115996#GiXVpYpbgUmfEo92qmfGe8vR8EKSi5GNsFuWPPowS5j6

@jcantrill jcantrill changed the title Fix generation output configuration if used receiver input LOG-7948: Fix generation output configuration if used receiver input Oct 28, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 28, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 28, 2025

@vparfonov: This pull request references LOG-7948 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.8.0" version, but no target version was set.

In response to this:

Description

/cc @jcantrill
/assign @jcantrill

Links

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.

@jcantrill
Copy link
Contributor

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 28, 2025
@jcantrill
Copy link
Contributor

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 30, 2025
@vparfonov
Copy link
Contributor Author

/retest

@vparfonov
Copy link
Contributor Author

/test e2e-target

@jcantrill
Copy link
Contributor

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 4, 2025
@jcantrill
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, vparfonov

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

The pull request process is described 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

@vparfonov
Copy link
Contributor Author

/test e2e-target

@jcantrill
Copy link
Contributor

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 4, 2025

@vparfonov: 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-merge-bot openshift-merge-bot bot merged commit 3fd6d9f into openshift:master Nov 4, 2025
7 checks passed
@vparfonov vparfonov deleted the log7948 branch November 4, 2025 15:37
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. release/6.4

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants