Skip to content

Bug 1762409: Fix memory dereference bug in eventrouter#1768

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.2from
openshift-cherrypick-robot:cherry-pick-1766-to-release-4.2
Nov 2, 2019
Merged

Bug 1762409: Fix memory dereference bug in eventrouter#1768
openshift-merge-robot merged 1 commit intoopenshift:release-4.2from
openshift-cherrypick-robot:cherry-pick-1766-to-release-4.2

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #1766

/assign richm

https://bugzilla.redhat.com/show_bug.cgi?id=1756920
This tries to keep the functionality the same in 4.x as it was
in 3.x.  In 3.x, you had to:

- deploy the eventrouter with a pod name like "logging-eventrouter-*"
- deploy the eventrouter in the default namespace
- set `TRANSFORM_EVENTS=true`
- set `MERGE_JSON_LOG=true` (which was the default in 3.x)

In 4.x, the pod name changes to "eventrouter-*" to follow the convention
of our other logging pods.  The eventrouter defaults to running
in "openshift-logging" - it doesn't really matter, as long as it is
running in an "infra" namespace.  This change also enables
`MERGE_JSON_LOG=true` for eventrouter pods.
The biggest problem is that you have to set the cluster to unmanaged
in order to set `TRANSFORM_EVENTS=true`.  We could workaround that
by making `TRANSFORM_EVENTS=true` the default value.  That would
cause every kubernetes record to be checked to see if it looks like
and event, and process it as such if it matches.  I'm not sure what
the performance implications would be.
Also ports eventrouter test to 4.x
Also adds a test for eventrouter Info type support

update eventrouter to pick up fix for Bug 1701495
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: An error was encountered searching for bug 1756920 on the Bugzilla server at https://bugzilla.redhat.com:

did not get one bug, but 0: {[]}
Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

Details

In response to this:

[release-4.2] Bug 1756920: fluentd pods do not process kubernetes events

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-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 16, 2019
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

Bug 1762409 - Eventrouter pod in CrashLoopBackOff status: "runtime error: invalid memory address or nil pointer dereference"

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.

@richm richm changed the title [release-4.2] Bug 1756920: fluentd pods do not process kubernetes events Bug 1762409 - Eventrouter pod in CrashLoopBackOff status: "runtime error: invalid memory address or nil pointer dereference" Oct 16, 2019
@richm richm changed the title Bug 1762409 - Eventrouter pod in CrashLoopBackOff status: "runtime error: invalid memory address or nil pointer dereference" Bug 1762409: Eventrouter pod in CrashLoopBackOff status: "runtime error: invalid memory address or nil pointer dereference" Oct 16, 2019
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1762409, which is invalid:

  • expected dependent Bugzilla bug 1701495 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 1762409: Eventrouter pod in CrashLoopBackOff status: "runtime error: invalid memory address or nil pointer dereference"

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-ci-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Oct 16, 2019
@richm richm added kind/bug Categorizes issue or PR as related to a bug. release/4.2 and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Oct 16, 2019
@richm
Copy link
Contributor

richm commented Oct 17, 2019

/retest

@richm
Copy link
Contributor

richm commented Oct 17, 2019

aws flake
/retest

@richm
Copy link
Contributor

richm commented Oct 17, 2019

strange flake with api.ci registry? all of the other fluentd pods were fine

fluentd-pcrb8                                   0/1     ImagePullBackOff   0          14m

/retest

@richm
Copy link
Contributor

richm commented Oct 17, 2019

aws flake
/retest

@richm
Copy link
Contributor

richm commented Oct 18, 2019

level=fatal msg="failed to initialize the cluster: Cluster operator monitoring is still updating"

flake?
/retest

@richm
Copy link
Contributor

richm commented Oct 30, 2019

/bugzilla refresh

@openshift-ci-robot
Copy link

@richm: This pull request references Bugzilla bug 1762409, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/bugzilla refresh

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-ci-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Oct 30, 2019
@richm
Copy link
Contributor

richm commented Oct 30, 2019

/bugzilla refresh

@openshift-ci-robot
Copy link

@richm: This pull request references Bugzilla bug 1762409, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

/bugzilla refresh

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-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Oct 30, 2019
@richm
Copy link
Contributor

richm commented Oct 30, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 30, 2019
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, richm

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 30, 2019
@richm
Copy link
Contributor

richm commented Oct 30, 2019

NOTE to openshift patch manager/cherry-pick approver - this doesn't really fix Bug 1762409: Eventrouter pod in CrashLoopBackOff status: "runtime erro - the real fix for that bug was done in origin/eventrouter, fixed in the openshift-eventrouter rpm, and built into the eventrouter image. This PR is primarily for adding an eventrouter test for that BZ. Also, this BZ enhances the eventrouter test which blocks other PRs/BZs which depend on that test.

@crawford
Copy link

crawford commented Nov 1, 2019

/retitle Bug 1762409: Fix memory dereference bug in eventrouter

@crawford crawford changed the title Bug 1762409: Eventrouter pod in CrashLoopBackOff status: "runtime error: invalid memory address or nil pointer dereference" Bug 1762409: Fix memory dereference bug in eventrouter Nov 1, 2019
@crawford
Copy link

crawford commented Nov 1, 2019

@crawford crawford added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 1, 2019
@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit af20a35 into openshift:release-4.2 Nov 2, 2019
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged. Bugzilla bug 1762409 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1762409: Fix memory dereference bug in eventrouter

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.

@richm
Copy link
Contributor

richm commented Nov 4, 2019

/cherrypick release-4.1

@openshift-cherrypick-robot
Copy link
Author

@richm: new pull request created: #1777

Details

In response to this:

/cherrypick release-4.1

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release/4.2 size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants