Clone and Rehydrate may overwrite blobs when destination checks fail

Aperta
  • Qualcosa non va?
#9,233 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
azure
Ambito
cloud, desktop-dev

Direzione di ricerca

Start in the Clone and Rehydrate flow, tracing how the destination-blob existence checks, the container check and the subsequent copy are sequenced, and how a failed blob check is interpreted as a missing destination. The payload names no specific files or tests, so locate them from those function names. Done means a reproduction with injected check failures, plus either a blocked Apply or an explicit overwrite confirmation, and the maintainers have agreed on the intended behaviour.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Source inspection identified a potential data-loss risk in Clone and Rehydrate. If the destination-existence checks both fail, the operation may treat an existing blob as absent and overwrite it. This has not been reproduced, and no data loss has been verified.

Conditions to investigate
  • The destination container exists and its initial container check succeeds.
  • A blob with the selected destination name already exists.
  • Both the destination-blob property check and the listing check fail, for example because of transient errors or permissions that allow the container check and copy but prevent blob reads and listing.
  • A subsequent copy request succeeds.
Proposed reproduction (not yet run)

Use disposable test data, not a production account.

  1. Create an archived source blob and an existing destination blob.
  2. Arrange for both destination-blob existence checks to fail while allowing the initial container check and the subsequent copy to succeed. The exact permission configuration or failure injection still needs to be established.
  3. Open Clone and Rehydrate, enter the existing destination name, and observe whether Apply is enabled and whether the existing blob is overwritten.
Expected experience

If the destination cannot be checked, the operation should report the failure and avoid silently overwriting an existing blob.

Actual experience

Not observed. Source inspection suggests that failures of both blob-existence checks can be treated as a missing destination, enabling Apply, and that the subsequent copy has no overwrite condition or separate confirmation. In contrast, a failed container-existence check prevents Apply, although its message may say the container does not exist.

Environment and related report

Storage Explorer version, build, operating system, architecture, authentication method, and an exact reproducing permission setup have not been verified. A previous same-name warning report is closed; it did not describe failures of both existence checks.

Lingua principale
Nessun dato sulla lingua
Stelle
458
Fork
92
Merge medio
17h 57m
PR unite (30g)
4

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/AzureStorageExplorer

Tutte le issue di microsoft/AzureStorageExplorer

Issue simili

Altre issue su Cloud

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.