Fix functional tests failures for STF tests#166
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. |
410547e to
3190efb
Compare
3190efb to
a771ce8
Compare
| changed_when: false | ||
| failed_when: container_nodes.stdout_lines|length != 0 | ||
|
|
||
| - name: Check what metrics are available to prometheus that relate to sensubility |
There was a problem hiding this comment.
@lnatapov I think that making this a new test would be a good idea.
It validates a pre-req for later sensubility tests i.e. There are sensubility metrics available
There was a problem hiding this comment.
It would need a failed_when condition to make it useful
ea0fbf3 to
c89d25f
Compare
ayefimov-1
left a comment
There was a problem hiding this comment.
A few comments that have not been resolved but looks fine to me.
* Update the alarm to use FVT_TESTING in the alarm description so we can identify the alarm created by this test * Replace grep with an updated failed_when condition * Correct the failed_when condition to match the alarm message
* Retry the check for alarm creation TODO: * Add check for Prometheus rule deletion
Fix ansible-lint errors
This avoids some errors in parsing the alertmanager config, which caused delays and the alarm not to appear in the logs
Increase retry count.
…n_alert_manager.yml
25c8f8b to
93eac82
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