OBSDOCS-2747: Reapply syslog receiver verification fix for 6.6#115876
OBSDOCS-2747: Reapply syslog receiver verification fix for 6.6#115876johnwilkins wants to merge 1 commit into
Conversation
Fix syslog receiver verification to use logger instead of curl. This reapplies the fix from PR openshift#114615 which was inadvertently reverted by PR openshift#114845 (OBSDOCS-1639). The curl command sends HTTP requests, not syslog messages, so it cannot properly test a syslog receiver. The logger command uses the syslog protocol and is the correct tool for verification. Changes: - Removed curl-based verification including CA certificate extraction - Replaced with proper logger command that uses the syslog protocol - Simplified verification to a single step with the correct tool This fix is already applied to versions 6.3, 6.4, and 6.5 via the original OBSDOCS-2747 cherry-picks. Signed-off-by: John Wilkins <jowilkin@redhat.com>
openshift-ci-robot
added
the
jira/valid-reference
|
@johnwilkins: This pull request references OBSDOCS-2747 which is a valid jira issue. DetailsIn 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-ci
Bot
added
the
size/S
|
🤖 Mon Jul 20 18:15:15 - Prow CI generated the docs preview: |
|
@johnwilkins: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
3 participants
Summary
Reapply the syslog receiver verification fix that was inadvertently reverted by PR #114845 (OBSDOCS-1639).
Problem: PR #114845 merged on July 8th and reverted the OBSDOCS-2747 fix that was merged on July 6th. The original fix replaced the incorrect
curlverification method with the properloggercommand.Changes:
loggercommand that uses the syslog protocolWhy this matters: The
curlcommand sends HTTP requests, not syslog messages, so it cannot properly test a syslog receiver. Theloggercommand uses the syslog protocol and is the correct tool.Status on other versions:
JIRA: https://redhat.atlassian.net/browse/OBSDOCS-2747
Signed-off-by: John Wilkins jowilkin@redhat.com