You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
telegraf-1.17.1+ (versions before are ok), RHEL 8.3 and CentOS 7.9
Steps to reproduce:
Setup a x509_cert input which has multiple servers in the sources block, where they each resolve to different hostnames (cert for server1 is not valid for server2, etc)
telegraf --config sslcert-check.conf --test
Expected behavior:
As long as all certificates in the sources list are valid there should be no verification errors reported.
Actual behavior:
Verification errors are printed like so:
# telegraf --config sslcert-check.conf --test | egrep -o 'verification_error=".*"'
verification_error="x509: certificate is valid for web2.domain.edu not web1.domain.edu"
verification_error="x509: certificate is valid for web3.domain.edu not web1.domain.edu"
From the errors it looks like it's trying to verify all certs listed against the hostname for the first server given in the list.
Additional info:
Same config has no such errors prior to version 1.17.1.
Breaking each server out into individual checks is still fine and gives no issues:
Did not come across that issue number since I was searching for the verification_error message I was getting which wasn't pasted over there. Will close this out.
Relevant telegraf.conf:
System info:
telegraf-1.17.1+ (versions before are ok), RHEL 8.3 and CentOS 7.9
Steps to reproduce:
Expected behavior:
As long as all certificates in the sources list are valid there should be no verification errors reported.
Actual behavior:
Verification errors are printed like so:
From the errors it looks like it's trying to verify all certs listed against the hostname for the first server given in the list.
Additional info:
Same config has no such errors prior to version 1.17.1.
Breaking each server out into individual checks is still fine and gives no issues:
But would still be nice to have the old behavior where one [[inputs.x509_cert]] block could include all the servers needed to be monitored.
The text was updated successfully, but these errors were encountered: