-
Notifications
You must be signed in to change notification settings - Fork 4
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
First pass at resolving the snmp test failures #166
base: master
Are you sure you want to change the base?
Conversation
b8ffcb7
to
ff8ef96
Compare
9f933df
to
3fda2d0
Compare
recheck |
17863ff
to
91990e9
Compare
8353e87
to
2503c4a
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
2503c4a
to
a381325
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
de97212
to
2d46452
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
08ab06b
to
410547e
Compare
Use rescue to provide additional information when the test fails
* update block contents * add always for cleanup tasks * Replace wait with a continuous check
* Update the alarm to use "fvt-tests" in the name and FVT_TESTING in the alarm description so we can identify the alarm created by this test * Delete the prometheusrule when the test is over * Correct the failed_when condition to match the alarm message * Update the check for the alarm to wait for up to 2 minutes. * Update timeout on alarm creation add a check for deletion
* Name the alarm for tracability * Retry the check for alarm creation * Add check for Prometheus rule deletion
This avoids some errors in parsing the alertmanager config, which caused delays and the alarm not to appear in the logs
410547e
to
3190efb
Compare
The issue may have been caused by the observability strategy tests causing both community and redhat monitoring components to be installed and shadowing the monitoring component definitions (prom, alertmanager, etc)
Depends-On: #177