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

Fluentbit configurator sticks around when creating enclaves concurrently and prevents new enclaves from being created #2568

Open
mslipper opened this issue Oct 16, 2024 · 1 comment · May be fixed by #2567
Labels
bug Something isn't working painful Painful bug

Comments

@mslipper
Copy link

What's your CLI version?

1.3.0

Description & steps to reproduce

When multiple processes try to create enclaves at the same time, sometimes the fluentbit configurator container sticks around. This then causes subsequent creations to fail. You can see an example of this here: https://app.circleci.com/pipelines/github/ethereum-optimism/optimism/68789/workflows/125efdd1-ffc2-4034-8517-80a841d856d2/jobs/2846767/parallel-runs/0/steps/0-104.

I tried my hand at fixing this here by adding a suffix to the container name: #2567.

Desired behavior

Concurrent enclaves should be created successfully.

What is the severity of this bug?

Painful; this is causing significant friction in my workflow.

What area of the product does this pertain to?

Other: anything not covered by the above

@mslipper mslipper added the bug Something isn't working label Oct 16, 2024
@github-actions github-actions bot added the painful Painful bug label Oct 16, 2024
@barnabasbusa barnabasbusa linked a pull request Oct 17, 2024 that will close this issue
@tedim52
Copy link
Contributor

tedim52 commented Oct 17, 2024

Ah I checked out the issue - I do think adding the suffix should solve the issue. Will take a look at your PR : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working painful Painful bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants