Administration › Sharing › Shares: show federated shares paused by a restore (#1072 U9) #1086

Open
opened 2026-11-03 05:32:24 +00:00 by Cordy · 0 comments
Owner

#1071's federated rows show active for a share that answers 503 after a storage restore (v0.6.392). That overstates access, which is the safe direction, but it is still wrong.

Proposal.

  • The status precedence gains paused-restore after paused-trash.
  • It reuses the owner's chip text spStatePausedRestore ("Paused: storage restored") and a tip naming the backup and the server.
  • The review count, the exports and the filter chips count it like the other pauses.
  • The overlay comes from restores.Store.FederatedPausedBy(pid, sent), as ocmShares does (internal/api/ocmrestore1072.go), and stays out of ocm.OutState.

Refs: #1072 decision U9, #1071.

#1071's federated rows show `active` for a share that answers 503 after a storage restore (v0.6.392). That overstates access, which is the safe direction, but it is still wrong. **Proposal.** - The status precedence gains `paused-restore` after `paused-trash`. - It reuses the owner's chip text `spStatePausedRestore` ("Paused: storage restored") and a tip naming the backup and the server. - The review count, the exports and the filter chips count it like the other pauses. - The overlay comes from `restores.Store.FederatedPausedBy(pid, sent)`, as `ocmShares` does (`internal/api/ocmrestore1072.go`), and stays out of `ocm.OutState`. Refs: #1072 decision U9, #1071.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1086
No description provided.