Repository navigation
Increase BackingStore existence check timeout to 30 minutes - #195
Merged
Merged
Conversation
Extend the timeout for waiting for NooBaa BackingStore creation from 5 minutes to 30 minutes to accommodate NooBaa's automatic AWS fallback behavior. Background: NooBaa operator has built-in platform detection that attempts to create AWS S3-backed storage when running on AWS. When AWS credentials are not available (common in sandbox environments), NooBaa has a hardcoded 10-minute timeout before automatically falling back to pv-pool backed storage. Timeline observed in production: - NooBaa created at T+0 - Attempts AWS S3 BackingStore creation (waits for credentials) - At T+10min: Automatic fallback to pv-pool BackingStore - At T+13min: BackingStore fully OPTIMAL Changes: - Increase retries from 30 to 180 (180 retries * 10 seconds = 30 minutes) - Keeps delay at 10 seconds for reasonable check frequency - Total wait time: 1800 seconds (30 minutes) vs previous 300 seconds (5 minutes) This timeout accounts for: - NooBaa's 10-minute AWS credential wait - BackingStore pod creation and initialization (~3 minutes) - 15+ minute buffer for slower clusters Tested-by: Production deployment observation on cluster cvmdm.sandbox2624.opentlc.com Resolves: Ansible timeout failures during ODF deployment on AWS without credentials
treddy08
requested review from
fridim,
rut31337,
stencell and
wkulhanek
as code owners
October 29, 2026 01:22
hararora123
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extend the timeout for waiting for NooBaa BackingStore creation from 5 minutes to 30 minutes to accommodate NooBaa's automatic AWS fallback behavior.
Background:
NooBaa operator has built-in platform detection that attempts to create AWS S3-backed storage when running on AWS. When AWS credentials are not available (common in sandbox environments), NooBaa has a hardcoded 10-minute timeout before automatically falling back to pv-pool backed storage.
Timeline observed in production:
Changes:
This timeout accounts for:
Tested-by: Production deployment observation on cluster cvmdm.sandbox2624.opentlc.com
Resolves: Ansible timeout failures during ODF deployment on AWS without credentials