Bug 1266827
| Summary: | [RFE] add confirmation step for manifest deletion (explaining when refresh will do, and when have to use delete) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Xixi <xdmoon> | ||||||
| Component: | Content Management | Assignee: | Brad Buckingham <bbuckingham> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Bruno Rocha <rochacbruno> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 6.1.1 | CC: | abalakht, bbuckingham, bkearney, chrobert, egolov, jcallaha, kdixon, mmccune, rjerrido, rochacbruno, walden, xdmoon, zhunting | ||||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature, PrioBumpGSS, PrioBumpPM, Triaged, UserExperience | ||||||
| Target Release: | Unused | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://projects.theforeman.org/issues/18696 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | rubygem-katello-3.0.0.137-1 | Doc Type: | Enhancement | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1446707 (view as bug list) | Environment: | |||||||
| Last Closed: | 2017-06-20 17:53:46 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: | 1115190, 1385841 | ||||||||
| Attachments: |
|
||||||||
|
Description
Xixi
2015-09-28 06:43:56 UTC
possible duplicate: Bug 1292242 - [RFE] Add explanation about what manifest refresh and delete do Per 6.3 planning, moving out non acked bugs to the backlog Deleting a subscription manifest is one of the most destructive operations that can be done in a Satellite organization. I am STRONGLY in support of giving the user a very stern warning requiring an additional confirmation before deleting a manifest. Manifest deletion means that - I have to reupload my manifest. - I have to reattach subs to - systems - hypervisors - activation keys. And while attaching subs is significantly better in Satellite 6.2.2+ this situation is best avoided. It is exceedingly rare to actually in a production scenario to have to DELETE a manifest. Created redmine issue for this sprint: http://projects.theforeman.org/issues/18696 Chris, can you please bump this to the top of your queue. We are getting feedback it would be a big win for CEE. Upstream bug assigned to chrobert Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18696 has been resolved. Created attachment 1282630 [details]
no message in dialog screenshot
seems the message is not properly displayed in the popup dialog, see screenshot
Confirmed in satellite-6.2.10-2.0.el7sat.noarch as the attachment above, the dialog is displayed but missing the message. Created attachment 1285583 [details]
Verified: popup dialog is working
verified in satellite-6.2.10-3.0.el7sat.noarch
I accidentally changed the assignee.. fixing it. 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, 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/RHBA-2017:1553 |