Created attachment 1534190 [details]
Description of problem:
Showing empty discovery repo for repo url containing module streams
Version-Release number of selected component (if applicable):
Satellite 6.5 Snap 13
Steps to Reproduce:
1. Navigate to Discovery
2. Try to create discovery for repo url has the module streams
e.g. https://partha.fedorapeople.org/test-repos/rpm-with-modules/29/, https://partha.fedorapeople.org/test-repos/rpm-with-modules/e18/
Url is accepted and showing blank record
Records shown should not be empty, if not supported give an error message
expected result not sure in this case but it does not make sense to show blank record.
I was testing this scenario out with the fix being introduced for bug 1685437.
With that PR checked out, I am not seeing the same behavior.
Doing a discovery with 'https://partha.fedorapeople.org/test-repos/rpm-with-modules/29/', locates a repository at /.
Doing a discovery with ' https://partha.fedorapeople.org/test-repos/rpm-with-modules/', locates 3 repositories at /f28/, /f29/ and /el8/.
I was then able to create product/repo and sync the repository.
If you have that PR still checked out, mind taking a quick look and let me know if you see the same and if we should keep this one open for tracking?
Just tested this https://github.com/Katello/katello/pull/7998. It has been resolved by showing '/' for an absoulte path and with relative url can see multiple repos. This is likely to fix this issue.
We should keep this as open as this issue was raised against the Satellite 6.5 Downstream. The fix is available on upstream, we can verify this or close it once available on the downstream build. This will be good for tracking and ensuring that the fix working in the downstream build.
I would think, we should keep this for tracking.
The fix for bug 1685437 has been merged and is making it's way to an official build (i.e. currently ON_DEV). I am going to move this one also to ON_DEV, so that it will go ON_QA for verification when the other bugzilla does.
Created attachment 1547701 [details]
Verified in Satellite 6.5 with Snap 19. This is fixed and attached screenshot.
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.