Bug #12503
openRegistries - auto_complete_search returning 404 every time user activates search field
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1277515
Description of problem:
There is 404 error in the console every time user clicks into Registries search field.
or no entity matching the query is found.
It is caused by calling
'https://<FQDN>/registries/auto_complete_search?search='
immediately after the search field is being clicked (sending an empty query)
Version-Release number of selected component (if applicable):
katello-2.2.0.16-1.el7sat.noarch
katello-certs-tools-2.2.1-1.el7sat.noarch
katello-common-2.2.0.16-1.el7sat.noarch
katello-debug-2.2.0.16-1.el7sat.noarch
katello-default-ca-1.0-1.noarch
katello-installer-2.3.20-1.el7sat.noarch
katello-installer-base-2.3.20-1.el7sat.noarch
katello-server-ca-1.0-1.noarch
katello-service-2.2.0.16-1.el7sat.noarch
How reproducible:
every time
Steps to Reproduce:
1. Navigate to Containers -> Registries
2. click into search bar
3. BONUS - type any query that yelds 0 results
4. spot 404 in browser console
Actual results:
query sent with parameter "search="
404 in the console
Expected results:
- the query shouldn't be sent with no parameters
- the server-side script should handle the request properly (no 404)
Additional info:
Updated by Dominic Cleal over 9 years ago
- Project changed from Foreman to Katello
- Triaged set to No
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release set to 86
- Triaged changed from No to Yes
Updated by Eric Helms about 9 years ago
- Status changed from New to Need more information
Has this been resolved with the Docker V2 updates?
Updated by Eric Helms about 9 years ago
- Translation missing: en.field_release changed from 86 to 143
Updated by Justin Sherrill almost 9 years ago
- Translation missing: en.field_release changed from 143 to 114