Bug 1500090

Created from redmine issue http://projects.theforeman.org/issues/21258

Upstream bug assigned to None

Upstream bug assigned to walden

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21258 has been resolved.

Created attachment 1453738 [details]
Products discovered repos page

Reproduced via instructions.

Tested on SNAP 8.

Issue 1:
Note that there are five empty rows (should be no rows).

FIXED

Issue 2: 
Note that the results are not paged. List filter should update count of objects and be paged as well.

NOT FIXED

Screens attached.

Created attachment 1453739 [details]
Products discovered repos page Pagination

The foreman tasks bulk search api itself does not support pagination and I don't have enough rails expertise to add a new feature to the bulk search API supporting pagination.  This should likely be an RFE to foreman tasks rather than a bug on the UI of this page as the UI can only work with what is given to it.

Thoughts on this Tom and Rox?

Also note that the PR itself (https://github.com/Katello/katello/pull/7013) simply removed the pagination from the page because the foreman bulk search API doesn't support pagination.  So I question if FailedQA is accurate in this case.

If the bug was triaged in as to be fixed, per the description, I'm of the opinion that it needs to be fixed/repaired to spec. 

I agree with the assessment that it is perhaps an RFE; I further recognize that the initial report is perhaps two separate issues and perhaps should be/should've been filed as such. 

That said, the filed issue, accepted by the triage team, did note pagination in the report.

We may be able to remedy this by filing a separate issues for the lack of pagination and triage the issue accordingly. As it exists right now, however, the issue is not resolved as it is written.

(In reply to Corey Welton from comment #13)
> If the bug was triaged in as to be fixed, per the description, I'm of the
> opinion that it needs to be fixed/repaired to spec. 
> 
> I agree with the assessment that it is perhaps an RFE; I further recognize
> that the initial report is perhaps two separate issues and perhaps should
> be/should've been filed as such. 
> 
> That said, the filed issue, accepted by the triage team, did note pagination
> in the report.
> 
> We may be able to remedy this by filing a separate issues for the lack of
> pagination and triage the issue accordingly. As it exists right now,
> however, the issue is not resolved as it is written.

That's fine by me.

Upstream bug assigned to walden

+1 to make pagination a separate low priority issue

I am going to re-associate the original redmine issue as it is addressing 'Issue 1'.  It should not have been removed.

Based on discussion with Tom and Jake in IRC, I have created a bug 1598555 to track 'Issue 2'.  That behavior is an RFE and is not required for beta.

I am also going to place this back in to POST.

If there are any concerns, please let me know. Thanks All!

VERIFIED 

@satellite 6.4 snap 14

Steps:

1. go to Content -> Products
2. click Repo Discovery
3. select Repository Type - 'Container Images'
4. enter Registry to Discover - 'registry.access.redhat.com'
5. click Discover

observation:

- No empty rows found on page Content -> Products -> Repository Discovery


Note: 
- Regarding Pagination issue there is a low priority bug 1598555 created for 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/RHSA-2018:2927