elastic/kibana

Kibana Snapshot and Restore UI does not list non-searchable snapshot backing indices for a data stream restore

Open

#179,221 opened on Mar 22, 2024

View on GitHub
 (7 comments) (0 reactions) (1 assignee)TypeScript (8,021 forks)batch import
Feature:Snapshot and RestoreTeam:Kibana Managementbuggood first issuetriage_needed

Repository metrics

Stars
 (19,065 stars)
PR merge metrics
 (Avg merge 1d 16h) (999 merged PRs in 30d)

Description

Kibana version: 7.17.8 Elastic Cloud

Elasticsearch version: 7.17.8 Elastic Cloud

Describe the bug: When attempting to restore a backing index from a data stream using the Kibana -> Stack Management -> Snapshot and Restore UI. The UI does not find the backing index even though it is listed in the snapshot.

Steps to reproduce:

  1. Create data stream that is saved to snapshots but not part of any searchable snapshots.
  2. Verify that backing indices exist in a snapshot
  3. Try to restore the same backing index using the Kibana UI which will give you the error below:

There is a workaround for this by using the Restore API.

Expected behavior: The UI should allow you to restore an index like this the same way the Restore API does. The code is filtering out any backing indices, if that can be removed it should fix this.

Contributor guide

Research direction
Inspect the filtering logic in step logistics.tsx and remove the line that excludes backing indices to allow restore via UI.
Tech stack
typescript
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75