Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the proper parameter for SNMP timeout #435

Merged
merged 2 commits into from
Jun 13, 2023

Conversation

leifmadsen
Copy link
Member

The SNMP_TIMEOUT environment variable in the manifest_snmp_traps.j2
template for Service Telemetry Operator uses the wrong parameter,
passing port instead of timeout value to the template.

This change updates the template to use the appropriate parameter as
input.

Closes: rhbz#2213016

The SNMP_TIMEOUT environment variable in the manifest_snmp_traps.j2
template for Service Telemetry Operator uses the wrong parameter,
passing port instead of timeout value to the template.

This change updates the template to use the appropriate parameter as
input.

Closes: rhbz#2213016
@leifmadsen leifmadsen requested review from csibbitt and vkmc June 6, 2023 21:20
@leifmadsen
Copy link
Member Author

I haven't tested this yet. I made this change based on looking at the contents when I was looking at something else to close out an issue. Oops!

@leifmadsen
Copy link
Member Author

/test

@leifmadsen
Copy link
Member Author

test

@leifmadsen
Copy link
Member Author

I should probably do a real test here before merging to make sure I have all the proper parameters aligned and that changing the CR results in what I expect. I have that on my list for this sprint and should be able to get this merged soon. Thanks for the review!

@leifmadsen
Copy link
Member Author

I was testing spin up of OCP on PSI and it resulted in a working cluster.

I deployed this branch against that cluster and performed some verification.

  • deployed from index image
  • checked current values for timeout in ServiceTelemetry object and in default-snmp-webhook pod. Noted value for TIMEOUT was 1
  • changed ServiceTelemetry object alerting.alertmanager.receivers.snmpTraps.timeout from a value of 1 to 5
  • watch STO logs waiting for changes to happen, which they did
  • verified default-snmp-webhook pod restarted after changes. Confirmed.
  • checked default-snmp-webhook TIMEOUT value was updated to a value of 5

This issue is verified. I will merge it now.

@leifmadsen leifmadsen merged commit 9eacaf4 into master Jun 13, 2023
@leifmadsen leifmadsen deleted the fix/invalid-snmp-template-parameter branch June 13, 2023 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants