Skip to content

Update legacy log forward doc per Jeff #20610

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 20, 2020

Conversation

mburke5678
Copy link
Contributor

No description provided.

@openshift-docs-preview-bot

The preview will be available shortly at:

Copy link

@jcantrill jcantrill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2020
@mburke5678 mburke5678 added this to the Next Release milestone Mar 20, 2020
@mburke5678 mburke5678 merged commit 1d9aa97 into openshift:master Mar 20, 2020
@mburke5678 mburke5678 deleted the logging-legacy-forward branch March 20, 2020 15:34
@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.3

@openshift-cherrypick-robot

@mburke5678: new pull request created: #20611

In response to this:

/cherrypick enterprise-4.3

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/test-infra repository.

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.4

@openshift-cherrypick-robot

@mburke5678: new pull request created: #20612

In response to this:

/cherrypick enterprise-4.4

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/test-infra repository.

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.2

@openshift-cherrypick-robot

@mburke5678: #20610 failed to apply on top of branch "enterprise-4.2":

.git/rebase-apply/patch:24: trailing whitespace.
To configure {product-title} to send logs using *out_forward*, create a ConfigMap called `secure-forward` in the `openshift-logging` namespace that points to a receiver. 
warning: 1 line adds whitespace errors.
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	modules/cluster-logging-collector-external.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/cluster-logging-collector-external.adoc
CONFLICT (content): Merge conflict in modules/cluster-logging-collector-external.adoc
Patch failed at 0001 Update legacy log forward doc per Jeff

In response to this:

/cherrypick enterprise-4.2

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/test-infra repository.

@openshift-cherrypick-robot

@mburke5678: #20610 failed to apply on top of branch "enterprise-4.2":

.git/rebase-apply/patch:24: trailing whitespace.
To configure {product-title} to send logs using *out_forward*, create a ConfigMap called `secure-forward` in the `openshift-logging` namespace that points to a receiver. 
warning: 1 line adds whitespace errors.
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	modules/cluster-logging-collector-external.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/cluster-logging-collector-external.adoc
CONFLICT (content): Merge conflict in modules/cluster-logging-collector-external.adoc
Patch failed at 0001 Update legacy log forward doc per Jeff

In response to this:

/cherrypick enterprise-4.2

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/test-infra repository.

@openshift-cherrypick-robot

@mburke5678: new pull request could not be created: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:enterprise-4.4 and openshift-cherrypick-robot:cherry-pick-20610-to-enterprise-4.4"}],"documentation_url":"https://developer.github.com/v3/pulls/#create-a-pull-request"}

In response to this:

/cherrypick enterprise-4.4

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/test-infra repository.

@openshift-cherrypick-robot

@mburke5678: #20610 failed to apply on top of branch "enterprise-4.2":

.git/rebase-apply/patch:24: trailing whitespace.
To configure {product-title} to send logs using *out_forward*, create a ConfigMap called `secure-forward` in the `openshift-logging` namespace that points to a receiver. 
warning: 1 line adds whitespace errors.
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	modules/cluster-logging-collector-external.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/cluster-logging-collector-external.adoc
CONFLICT (content): Merge conflict in modules/cluster-logging-collector-external.adoc
Patch failed at 0001 Update legacy log forward doc per Jeff

In response to this:

/cherrypick enterprise-4.2

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/test-infra repository.

@openshift-cherrypick-robot

@mburke5678: new pull request could not be created: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:enterprise-4.3 and openshift-cherrypick-robot:cherry-pick-20610-to-enterprise-4.3"}],"documentation_url":"https://developer.github.com/v3/pulls/#create-a-pull-request"}

In response to this:

/cherrypick enterprise-4.3

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/test-infra repository.

1 similar comment
@openshift-cherrypick-robot

@mburke5678: new pull request could not be created: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:enterprise-4.3 and openshift-cherrypick-robot:cherry-pick-20610-to-enterprise-4.3"}],"documentation_url":"https://developer.github.com/v3/pulls/#create-a-pull-request"}

In response to this:

/cherrypick enterprise-4.3

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/test-infra repository.

@openshift-cherrypick-robot

@mburke5678: new pull request could not be created: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:enterprise-4.4 and openshift-cherrypick-robot:cherry-pick-20610-to-enterprise-4.4"}],"documentation_url":"https://developer.github.com/v3/pulls/#create-a-pull-request"}

In response to this:

/cherrypick enterprise-4.4

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/test-infra 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.

5 participants