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

E2E: Broker config test failing #322

Open
Haarolean opened this issue Apr 26, 2024 · 0 comments
Open

E2E: Broker config test failing #322

Haarolean opened this issue Apr 26, 2024 · 0 comments
Labels
scope/AQA Vlad really needed a separate label scope/backend Related to backend changes status/triage/completed Automatic triage completed type/bug Something isn't working

Comments

@Haarolean
Copy link
Member

          @Haarolean hey, I've faced failed brokersConfigEditCheck at this PR

and while investigation really reproduced it locally. it's not because of test :)

Possibly a bug

Brokers -> open one -> Configs tab -> search for 'log.cleaner.min.compaction.lag.ms'
Edit-> set new value -> Save -> Confirm

I really saw twice when after setting new value there's displayed old one

Originally posted by @VladSenyuta in #271 (comment)

@kapybro kapybro bot added status/triage Issues pending maintainers triage status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Apr 26, 2024
@Haarolean Haarolean added scope/AQA Vlad really needed a separate label scope/backend Related to backend changes type/bug Something isn't working labels Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/AQA Vlad really needed a separate label scope/backend Related to backend changes status/triage/completed Automatic triage completed type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant