-
Notifications
You must be signed in to change notification settings - Fork 44
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
Bug report: Alarm is not fired for certain detected bugs #224
Comments
Will sync with @Spedoske on this |
This looks like a very serious problem. If the alarm is not fired for silent, non-crashing issues, then the tool is broken at this point. |
Discussed with @Spedoske. The reason for bug 992 is because it is not supposed to be found by the consistency oracle, it is supposed to be found by the differential oracle. But the differential oracle is not being automatically run inside the acto_main.py, but run through a separate entry point. I fixed it a while ago by including the entrypoint inside acto_main.py so that it will be run automatically next time: https://github.com/xlab-uiuc/acto/tree/run_difftest_in_acto. Line 54 in 26ced42
Will close this after https://github.com/xlab-uiuc/acto/tree/run_difftest_in_acto gets merged, @Spedoske will help test if the change works or not. I think having a routined test is becoming important to help us make sure everything works and merge things quickly. I started writing tests for each bug in the /test directory, but it is still very incomplete. We should also have e2e test too. Todos before closing this:
|
I opened an issue to keep track of the cleanup tasks #222 , and we should keep adding and picking up tasks in that list as Kashun uses Acto. |
Resolved. |
I was trying to reproduce two bugs of the three detected bugs in Rabbitmq Operator, which is documented in
bugs.md
.rabbitmq/cluster-operator#992
rabbitmq/cluster-operator#928
Bug #992
Acto changed
storageClassName
, and there is no changes in PVC. So there should be an alarm for inconsistency.(trial-00-0006)
Bug # 928
The state 1 is shown as the following yaml file.
(trial-02-0023)
The state 2 is shown as the following yaml file.
We found that
override.statefulSet.spec.template.spec.affinity
becomenull
, but there is no change in system delta.So there should be an alarm for inconsistency, but Acto did not alarm.
The text was updated successfully, but these errors were encountered: