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

Chaos processes produce lots of version numbers #123

Open
pihme opened this issue Mar 8, 2022 · 5 comments
Open

Chaos processes produce lots of version numbers #123

pihme opened this issue Mar 8, 2022 · 5 comments
Labels
enhancement New feature or request Impact: Low The issue has an low impact on the system.

Comments

@pihme
Copy link
Contributor

pihme commented Mar 8, 2022

Some of the chaos experiment processes produce a new versions whenever they are deployed or executed:
image

The 100 seems to be a cap in Operate dashboard. The actual version number is 246. Most likely the processes are generated and use ramdom element IDs each time

@pihme pihme added enhancement New feature or request Impact: Low The issue has an low impact on the system. labels Mar 8, 2022
@pihme pihme changed the title Chaos: Chaos processes produce lots of version numbers Mar 8, 2022
@pihme
Copy link
Contributor Author

pihme commented Mar 8, 2022

🤡 But then again, it's chaos tests, so maybe this is a deliberate attempt to over time flood the state with BPMN versions 🤡

@Zelldon
Copy link
Member

Zelldon commented Mar 8, 2022

Looks for me like a bug

@Zelldon
Copy link
Member

Zelldon commented Mar 8, 2022

@pihme
Copy link
Contributor Author

pihme commented Mar 8, 2022

I guess I can delete the ones in testbench, because this here is the SSOT?

@Zelldon
Copy link
Member

Zelldon commented Dec 21, 2022

We still need to deploy the process models from zbchaos to testbench, possible first step in the docker image.

ghost pushed a commit to zeebe-io/zeebe-cluster-testbench that referenced this issue Dec 23, 2022
600: Remove chaos files r=Zelldon a=pihme

This PR removes the chaos files. 

Most of the files have already been moved to chaos test. However, some files are duplicated which leads to confusion and possibly to unintended outcomes: zeebe-io/zeebe-chaos#123

With the upcoming changes (i.e. Deepthi implementing another test) this repo will be slimmed down to only provide the bare testbench, which is then extensible by independently deployed tests (chaos tests, the Deepthi test).

`@Zelldon` Happy to discuss this direction of travel with you, if you have any objections. This is not set in stone. Since you were off this week, I didn't yet have a chance to align. This PR was created under the assumption that you agree to this approach.

`@Zelldon` I checked whether all the stuff I removed here is available in chaos-test. This seems true for the BPMN models and the deployment descriptors. However, I didn't immediately find any scripts to actually deploy the chaos workers. So this logic might have to be moved, or we just drop the last commit for a time being. 

Co-authored-by: pihme <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Impact: Low The issue has an low impact on the system.
Projects
None yet
Development

No branches or pull requests

2 participants