Skip to content

STAC-25303: document Azure container pre-creation requirement - #376

Merged
l4zy0n3 merged 2 commits into
mainfrom
STAC-25303
Aug 13, 2026
Merged

STAC-25303: document Azure container pre-creation requirement#376
l4zy0n3 merged 2 commits into
mainfrom
STAC-25303

Conversation

@l4zy0n3

@l4zy0n3 l4zy0n3 commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

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:

api error NoSuchBucket: The specified bucket does not exist

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-init does not help: it runs configure-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 IMPORTANT admonition to the Azure Blob Storage section, plus az storage container create examples for both documented layouts:

  • Containers must exist before backups run. Examples for the separate-containers layout (all five) and the single-container-with-prefixes layout (one).
  • The account must expose a Blob endpoint. A premium file shares (FileStorage) account has no Blob endpoint and cannot be used — it fails with java.net.UnknownHostException: <accountName>.blob.core.windows.net, which gives no clue as to the real cause. Recommends StorageV2 / BlockBlobStorage.
  • Azure container naming rules, since deployment-derived names can approach the 63-character limit.

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:

  1. A FileStorage account produced UnknownHostException with no indication the account kind was wrong.
  2. Once on a StorageV2 account, the first backup still failed with NoSuchBucket until 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-v2 CLI), #360 (v2 backup/restore docs).

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.
@l4zy0n3
l4zy0n3 requested a review from a team as a code owner August 3, 2026 09:53
@netlify

netlify Bot commented Aug 3, 2026

Copy link
Copy Markdown

Deploy Preview for suse-obs ready!

Name Link
🔨 Latest commit ee88b26
🔍 Latest deploy log https://app.netlify.com/projects/suse-obs/deploys/6a7d6e398a4b5e0008e5e185
😎 Deploy Preview https://deploy-preview-376--suse-obs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Co-authored-by: Akash Raj <akash.raj@suse.com>
@l4zy0n3
l4zy0n3 merged commit 1d251bc into main Aug 13, 2026
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants