Bug 1317871 - On pop-up confirming delete, name is ""
Summary: On pop-up confirming delete, name is ""
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: Zach Huntington-Meath
QA Contact: Kedar Bidarkar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 12:11 UTC by Zach Huntington-Meath
Modified: 2019-09-26 14:36 UTC (History)
3 users (show)

Fixed In Version: rubygem-katello-3.0.0.26-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:22:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 13120 0 None None None 2016-04-22 15:42:54 UTC

Description Zach Huntington-Meath 2016-03-15 12:11:49 UTC 
When deleting a sync plan, the pop up window will as 'Are you sure you want to remove Sync Plan ""?' where it should say  something along the lines of 'Are you sure you want to remove Sync Plan my_cool_sync_plan?'. This happens on content hosts as well, and probably other objects. To reproduce, create a sync plan and delete it.
Comment 1 Zach Huntington-Meath 2016-03-15 12:11:51 UTC 
Created from redmine issue http://projects.theforeman.org/issues/13120
Comment 3 Bryan Kearney 2016-03-21 14:06:16 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/13120 has been closed
-------------
Zach Huntington-Meath
Applied in changeset commit:katello|3e624ed03c617e2c4c093370dc9d6b481f10e4b1.
Comment 4 Kedar Bidarkar 2016-05-24 09:51:14 UTC 
1) Created a sync plan with name as "rhel7_sync_plan".
2) Deleted the sync plan by clicking "remove sync plan"

Which shows the below confirm dialog message as,

3)Are you sure you want to remove Sync Plan "rhel7_sync_plan"?

VERIFIED with sat62-snap12.1
Comment 5 Bryan Kearney 2016-07-27 11:22:23 UTC 
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-2016:1501
Note You need to log in before you can comment on or make changes to this bug.