OCPBUGS-32028: Decrease logs of haproxy

[mkowalski]

No description provided.

[openshift-ci-robot]

@mkowalski: This pull request references Jira Issue OCPBUGS-29919, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @zhaozhanqi

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

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.

[mkowalski]

/cc @cybertron

[mkowalski]

/retest-required

[zhaozhanqi]

@mkowalski sounds like below logs still print after changing to

# oc rsh -n openshift-kni-infra haproxy-master-0
Defaulted container "haproxy" out of: haproxy, haproxy-monitor, verify-api-int-resolvable (init)
sh-4.4$ cat /etc/haproxy/haproxy.cfg | grep log
  log     /var/run/haproxy/haproxy-log.sock local0 notice alert
  log-format "%ci:%cp -> %fi:%fp [%t] %ft %b/%s %Tw/%Tc/%Tt %B %ts %ac/%fc/%bc/%sc/%rc %sq/%bq"
  option  dontlognull
  option dontlognull
   option  log-health-checks



<134>Mar 12 01:41:01 haproxy[46]: ::ffff:192.168.111.1:53422 -> ::ffff:192.168.111.20:9445 [12/Mar/2024:01:40:28.063] main masters/master-1 1/0/33700 15180 -- 97/97/96/36/0 0/0
<134>Mar 12 01:41:03 haproxy[46]: ::ffff:192.168.111.25:49302 -> ::ffff:192.168.111.20:9445 [12/Mar/2024:01:41:03.173] main masters/master-0 1/0/4 2850 -- 98/98/97/53/0 0/0
<134>Mar 12 01:41:03 haproxy[46]: ::ffff:192.168.111.25:49304 -> ::ffff:192.168.111.20:9445 [12/Mar/2024:01:41:03.173] main masters/master-1 1/0/6 2858 -- 97/97/96/36/0 0/0
<134>Mar 12 01:41:05 haproxy[46]: ::ffff:192.168.111.1:47856 -> ::ffff:192.168.111.20:9445 [12/Mar/2024:01:41:04.228] main masters/master-2 1/0/1258 16319 -- 98/98/97/7/0 0/0

[mkowalski]

I just modified to remove log-health-checks option. Maybe this is what was logged

[zhaozhanqi]

Yes, the logs do not show up after removing log-health-checks

[openshift-ci]

@mkowalski: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-azure-ovn-upgrade-out-of-change	743fd42	link	false	/test e2e-azure-ovn-upgrade-out-of-change
ci/prow/okd-scos-e2e-aws-ovn	743fd42	link	false	/test okd-scos-e2e-aws-ovn

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/test-infra repository. I understand the commands that are listed here.

[mkowalski]

/cc @cybertron

In my opinion access logs for haproxy are not really useful, I do not recall us ever looking into them

[mkowalski]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@mkowalski: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.15

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]

@mkowalski: This pull request references Jira Issue OCPBUGS-32028, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @zhaozhanqi

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

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.

[cybertron]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cybertron, mkowalski, sinnykumari

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 [sinnykumari]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-bot]

/retest-required

Remaining retests: 0 against base HEAD 0968179 and 2 for PR HEAD 743fd42 in total

[openshift-bot]

@mkowalski: Jira Issue OCPBUGS-32028: All pull requests linked via external trackers have merged:

• openshift/machine-config-operator#4245

Jira Issue OCPBUGS-32028 has been moved to the MODIFIED state.

In response to this:

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-cherrypick-robot]

@mkowalski: new pull request created: #4313

In response to this:

/cherry-pick release-4.15

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-machine-config-operator-container-v4.16.0-202404102343.p0.g23df276.assembly.stream.el9 for distgit ose-machine-config-operator.
All builds following this will include this PR.