Bug 2270237
Summary: | [CephFS - Snap Scheduler UI] - Retention field available during snap schedule create, but using it generates an error. | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | sumr |
Component: | Ceph-Dashboard | Assignee: | Ivo Almeida <ialmeida> |
Status: | CLOSED ERRATA | QA Contact: | sumr |
Severity: | high | Docs Contact: | Akash Raj <akraj> |
Priority: | unspecified | ||
Version: | 7.1 | CC: | akraj, ceph-eng-bugs, cephqe-warriors, ialmeida, nia, tserlin |
Target Milestone: | --- | ||
Target Release: | 7.1 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ceph-18.2.1-78.el9cp | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-06-13 14:29:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2267614, 2298578, 2298579 |
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Critical: Red Hat Ceph Storage 7.1 security, enhancements, and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:3925 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |
Created attachment 2022468 [details] snap_sched_ui_create_retention_both_fails Description of problem: 'Add retention policy' box exists in Snapshot schedule Create. It is enabled, so can be used to add retention policy during snap schedule create. But if used, upon 'Create Snapshot Schedule' button click, generates an error as in attached screenshot. Error : "Failed to add retention policy.....:No schedule found" This error could be expected. Because even in CLI, we need to first create schedule, and then for same path we can apply retention policy that gets applied to all existing schedules of same path. But as we have 'Add retention policy' enabled for use, during create, any user can use it and face above circumstances. So, we should with either support use of this retention button or remove it or disable it, as appropriate. Also, when "Failed to add retention policy.....:No schedule found" appears with 'Create snapshot schedule' click, if 'Add retention policy' was used, we also notice that, schedule gets created in background and an entry is made in list of schedules(refer screenshot). But for user, considering error seen as '"Failed to add retention policy.....:No schedule found"' , he may remove retention policies and try again 'Create snapshot schedule' button click, which generates error stating 'Path already exists'. So we displayed error as '"Failed to add retention policy.....:No schedule found"' but have created the schedule in background, no notification for creation either. Version-Release number of selected component (if applicable): 18.2.1-70.el9cp How reproducible: Steps to Reproduce: 1. In Snapshot schedules UI tab, Select create. 2. Add schedule for subvolume. Click 'Add retention policy' 3. Add retention policies, click 'Create snapshot schedule' Actual results: mentioned in 'Description' section. Expected results: 'Add retention policy' should not be available or disabled for create Additional info: