Bug 1079953 - deleting user notifications results in Monitor -> Content Dashboadr -> Latest Notifications -> More results in strange sequence of pop-up windows
Summary: deleting user notifications results in Monitor -> Content Dashboadr -> Lates...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-24 11:45 UTC by Jan Hutař
Modified: 2019-09-26 18:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 12:23:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
One workflow which did not worked for me (448.71 KB, image/png)
2014-03-24 11:45 UTC, Jan Hutař
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 6719 0 None None None 2016-04-22 16:16:08 UTC

Description Jan Hutař 2014-03-24 11:45:29 UTC
Created attachment 878011 [details]
One workflow which did not worked for me

Description of problem:
Deleting user notifications results in Monitor -> Content Dashboadr ->  Latest Notifications -> More results in strange sequence of pop-up windows


Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140321.2


How reproducible:
always


Steps to Reproduce:
1. In webUI go to Monitor -> Content Dashboadr ->  Latest Notifications ->
   -> <some_action> -> More
2. Click "Delete All"


Actual results:
Stream of strange confirmation dialogs and then all rows disappears even when you press "no" in one of them and also they disappear only till you refresh a page.


Expected results:
One confirmation dialog and way to actually delete these. It all should be consistent and when required, rows should be really deleted.


Additional info:
E.g. check workflow in attached screenshot:

1) click "Delete All"
2) Are you sure? - answer OK
3) Are you sure? - answer No
4) Check all rows are gone
5) Refresh the page
6) Some rows are back! (no screenshot for this now)

Also note text is barely visible in confirmation dialog 2.

Also note buttons are ordered differentially - "OK" is on the right in step 2) and "Yes" on the left in step 3).

"OK" and "Yes" is not consistent as well.

Comment 1 RHEL Program Management 2014-03-24 11:55:05 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Brad Buckingham 2014-07-22 13:13:58 UTC
Created redmine issue http://projects.theforeman.org/issues/6719 from this bug

Comment 4 Brad Buckingham 2014-07-22 16:07:21 UTC
Proposed fix in Katello PR:
   https://github.com/Katello/katello/pull/4469

Comment 6 sthirugn@redhat.com 2014-08-07 16:36:54 UTC
Verified.

1) click "Delete All" - working fine
2) Are you sure? - answer OK - working fine
3) Are you sure? - answer No - working fine
4) Check all rows are gone - working fine
5) Refresh the page - working fine
6) Some rows are back! (no screenshot for this now)  - working fine - the rows didnt come back.

Version Tested:
GA Snap 4 - Satellite-6.0.4-RHEL-6-20140806.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.19-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.19-1.el6_5.noarch
* candlepin-tomcat6-0.9.19-1.el6_5.noarch
* elasticsearch-0.90.10-4.el6sat.noarch
* foreman-1.6.0.38-1.el6sat.noarch
* foreman-compute-1.6.0.38-1.el6sat.noarch
* foreman-gce-1.6.0.38-1.el6sat.noarch
* foreman-libvirt-1.6.0.38-1.el6sat.noarch
* foreman-ovirt-1.6.0.38-1.el6sat.noarch
* foreman-postgresql-1.6.0.38-1.el6sat.noarch
* foreman-proxy-1.6.0.23-1.el6sat.noarch
* foreman-selinux-1.6.0.4-1.el6sat.noarch
* foreman-vmware-1.6.0.38-1.el6sat.noarch
* katello-1.5.0-28.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.57-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-3.el6sat.noarch
* pulp-nodes-common-2.4.0-0.30.beta.el6sat.noarch
* pulp-nodes-parent-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-tools-2.4.0-0.30.beta.el6sat.noarch
* pulp-rpm-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-selinux-2.4.0-0.30.beta.el6sat.noarch
* pulp-server-2.4.0-0.30.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch
* sssd-ldap-1.11.5.1-3.el6.x86_64

Comment 8 Bryan Kearney 2014-09-11 12:23:29 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.


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