Bug 1203111

Summary: Sync plan page shows incorrect count of Total plans after deleting the sync plans.
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: WebUIAssignee: Walden Raines <walden>
WebUI sub component: Katello QA Contact: Jitendra Yejare <jyejare>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: unspecified CC: bbuckingham
Version: 6.1.0Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: http://projects.theforeman.org/issues/14902
Whiteboard:
Fixed In Version: rubygem-katello-3.0.0.27-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:32:08 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:
Attachments:
Description Flags
Screenshot of Sync Plans page showing an incorrect Total Count of Sync plans.
none
Satellite 6.1.1: Sync plans before delete
none
Satellite 6.1.1: Sync plans after delete none

Description Jitendra Yejare 2015-03-18 06:51:54 UTC
Created attachment 1003079 [details]
Screenshot of Sync Plans page showing an incorrect Total Count of Sync plans.

Description of problem:
The Sync plan shows an incorrect number(count) of Total plans present on the page in label 'Showing <number> of <TotalCount>' also goes into minus.

Version-Release number of selected component (if applicable):
Satellite 6.1 Snap 6 Compose 2.

How reproducible:
Always

Steps to Reproduce:
1. Create 2 Sync plans from Content -> Sync Plans page.
2. Delete both of them.
3. Observe the total count in label 'Showing <num> of <TotalCount>'.

Actual results:
The Sync plan shows an incorrect number(count) of Total plans present on the page in label 'Showing <number> of <TotalCount>' also goes into minus.

Expected results:
The Total Count of sync plans on the page should be correct in label 'Showing <num> of <TotalCount>'.

Comment 2 Brad Buckingham 2015-09-02 18:41:44 UTC
I have tested this on a Satellite 6.1.1 GA install and am no longer observing
the behavior described.

RPMs:
ruby193-rubygem-katello-2.2.0.66-1.el7sat.noarch
foreman-1.7.2.34-1.el7sat.noarch

Updated screenshots attached.

Comment 3 Brad Buckingham 2015-09-02 18:42:15 UTC
Created attachment 1069572 [details]
Satellite 6.1.1: Sync plans before delete

Comment 4 Brad Buckingham 2015-09-02 18:42:44 UTC
Created attachment 1069573 [details]
Satellite 6.1.1: Sync plans after delete

Comment 5 Jitendra Yejare 2016-03-14 10:23:12 UTC
I tested this on latest Satellite 6.2 snap 3 beta.

I can see issue is still reproducible.

After adding two syn plans it shows 'Showing 2 of 0 (0 Total)' <- This is incorrect.

After Removing it shows properly now as 0 of 0.

I am using firefox to repro this issue.

Comment 6 Brad Buckingham 2016-03-14 13:28:24 UTC
Thanks Jitendra.  I was able to reproduce on upstream master now as well.

Comment 7 Walden Raines 2016-05-02 14:35:18 UTC
Created redmine issue http://projects.theforeman.org/issues/14902 from this bug

Comment 8 Walden Raines 2016-05-02 14:48:38 UTC
PR - https://github.com/Katello/katello/pull/6009

Comment 9 Walden Raines 2016-05-04 13:08:05 UTC
This should be in POST:

Revision a29e6105
Added by Walden Raines 2 days ago

Fixes #14902: refresh nutupane when adding/removing sync plans

The nutupane table wasn't being refreshed when adding or removing
sync plans and thus the count was off. This commit refreshes the
nutupane after altering the total number of sync plans.

http://projects.theforeman.org/issues/14902

Revision 8284fe2e
Added by Walden Raines about 15 hours ago

Merge pull request #6009 from waldenraines/14902

Fixes #14902: refresh nutupane when adding or removing sync plans.

Comment 10 Jitendra Yejare 2016-06-24 07:16:37 UTC
Verified.

@Sat 6.2 Snap 17

I added two sync plans and deleted them. The total count while adding/deleting and after adding/deleting is shown correctly.

So moving this bz to verified state.

Comment 11 Bryan Kearney 2016-07-27 11:32:08 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