STAC-25303: document Azure container pre-creation requirement - #376
Merged
Conversation
Enabling Azure Blob backups against a fresh storage account fails because nothing in SUSE Observability creates the BLOB containers. The backup job dies with 'NoSuchBucket: The specified bucket does not exist', and the docs gave no indication the containers were a prerequisite. Add an IMPORTANT admonition to the Azure Blob Storage section covering: - containers must exist before backups run, with az CLI examples for both the separate-containers and single-container-with-prefixes layouts - the account must expose a Blob endpoint; a premium file shares (FileStorage) account cannot work and fails with UnknownHostException - Azure container naming rules Found during manual QA of StackGraph backup/restore v2 against Azure.
✅ Deploy Preview for suse-obs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
akashraj4261
reviewed
Aug 4, 2026
akashraj4261
approved these changes
Aug 4, 2026
Co-authored-by: Akash Raj <akash.raj@suse.com>
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.
Problem
Enabling Azure Blob backups against a fresh storage account fails. Nothing in SUSE Observability creates the BLOB containers, so the first backup job dies with:
The docs currently mention the container names only descriptively — "backups are stored in BLOB containers called
sts-stackgraph-backup, ..." — which reads as a statement of fact, not a prerequisite.job-backup-initdoes not help: it runsconfigure-backup.sh, which only registers the Elasticsearch snapshot repository.Any customer pointing at a new storage account hits this on their first backup.
Changes
Adds an
IMPORTANTadmonition to the Azure Blob Storage section, plusaz storage container createexamples for both documented layouts:FileStorage) account has no Blob endpoint and cannot be used — it fails withjava.net.UnknownHostException: <accountName>.blob.core.windows.net, which gives no clue as to the real cause. RecommendsStorageV2/BlockBlobStorage.English source page only; translations not touched.
How this was found
Manual QA of StackGraph backup/restore v2 against Azure Blob (STAC-25303). Both failure modes were hit for real:
FileStorageaccount producedUnknownHostExceptionwith no indication the account kind was wrong.StorageV2account, the first backup still failed withNoSuchBucketuntil the container was created by hand.After pre-creating the container, backup and restore both passed end to end, including a data-correctness check (mutate → restore → state rolled back to the exact pre-backup fingerprint).
Note
The AWS S3 section already sets a precedent for this kind of callout — it explicitly documents that SSE-KMS is unsupported and quotes the resulting error. The Azure section had no equivalent.
Related: StackVista/stackstate-backup-cli#32 (unreleased
stackgraph-v2CLI), #360 (v2 backup/restore docs).