Bug 1782847: sdn: undo debug logging

[squeed]

It was added to track down the informer issue; we caught it. It causes logs to be way too large.

[openshift-ci-robot]

@squeed: This pull request references Bugzilla bug 1782847, which is invalid:

• expected the bug to target the "4.4.0" release, but it targets "---" 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.

In response to this:

Bug 1782847:sdn: undo debug logging

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.

[squeed]

/bugzilla refresh

[openshift-ci-robot]

@squeed: This pull request references Bugzilla bug 1782847, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

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.

[squeed]

I want to backport this to 4.3.0 before it releases. Thus, this is pretty important. @juanluisvaladas can you review?

[danwinship]

/lgtm

[juanluisvaladas]

/lgtm
Commit with adding the additional logging: https://github.com/openshift/sdn/commit43452fe37f51a41ea1d56dd66dda9ae1d10bbda7

[openshift-bot]

/retest

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

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, juanluisvaladas, squeed

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:

• OWNERS [danwinship,squeed]

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]

@squeed: All pull requests linked via external trackers have merged. Bugzilla bug 1782847 has been moved to the MODIFIED state.

In response to this:

Bug 1782847: sdn: undo debug logging

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.

[squeed]

/cherry-pick release-4.3

[squeed]

/cherrypick release-4.3

[openshift-cherrypick-robot]

@squeed: #84 failed to apply on top of branch "release-4.2":

error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	pkg/openshift-sdn/informers.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/openshift-sdn/informers.go
CONFLICT (content): Merge conflict in pkg/openshift-sdn/informers.go
Patch failed at 0001 sdn: undo debug logging

In response to this:

/cherry-pick release-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]

@squeed: new pull request created: #85

In response to this:

/cherry-pick release-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]

@squeed: failed to push cherry-picked changes in GitHub: pushing failed, output: "To https://github.com/openshift-cherrypick-robot/sdn\n ! [rejected] cherry-pick-84-to-release-4.3 -> cherry-pick-84-to-release-4.3 (fetch first)\nerror: failed to push some refs to 'https://openshift-cherrypick-robot:CENSORED@github.com/openshift-cherrypick-robot/sdn'\nhint: Updates were rejected because the remote contains work that you do\nhint: not have locally. This is usually caused by another repository pushing\nhint: to the same ref. You may want to first integrate the remote changes\nhint: (e.g., 'git pull ...') before pushing again.\nhint: See the 'Note about fast-forwards' in 'git push --help' for details.\n", error: exit status 1

In response to this:

/cherrypick release-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.