Bug 2166705 - [dashboard] block/rbd : images -> snapshots : disable protect option if layering feature is not enabled on the image
Summary: [dashboard] block/rbd : images -> snapshots : disable protect option if layer...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Dashboard
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 7.0
Assignee: avan
QA Contact: Sayalee
Anjana Suparna Sriram
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-02 17:10 UTC by Vasishta
Modified: 2023-08-09 10:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
dashboard snapshot (154.36 KB, image/png)
2023-02-02 17:10 UTC, Vasishta
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6072 0 None None None 2023-02-02 17:12:06 UTC
Red Hat Issue Tracker RHCSDASH-923 0 None None None 2023-02-02 17:12:44 UTC

Description Vasishta 2023-02-02 17:10:17 UTC
Created attachment 1941884 [details]
dashboard snapshot

Description of problem:
attempt to protect a snapshot of which layering is not enabled for image fails without giving much clue to user in dashboard.

(when tried in cli it throws error message saying layering needs to be enabled on the image)

So disable the option in dashboard if layering is not enabled.

Version-Release number of selected component (if applicable):
6.0 latest

How reproducible:
Alwasy

Steps to Reproduce:
1. Create an rbd image without layering feature.
2. create a snapshot
3. Try to protect snapshot from dashboard

Actual results:
error notification comes without giving clue

Expected results:
Disable protect option or ask users to enable layering feature

Additional info:

Comment 1 Scott Ostapovicz 2023-07-12 13:03:54 UTC
Missed the 6.1 z1 window.  Retargeted to 6.1 z2.


Note You need to log in before you can comment on or make changes to this bug.