1. Proposed title of this feature request [RFE] searching on a specific host's hosts/<id>/interfaces should only return the matching interface 3. What is the nature and description of the request? When querying the interfaces of a specific host and providing a search parameter that should narrow down the search, the results still return all of the interfaces. This RFE is to have the api for /hosts/<id>/interfaces only return the matching interface when a matching ?search= is provided. 4. Why does the customer need this? (List the business requirements here) For automation purposes. Now the api must be called, and then all of the results iterated and parsed to find the correct interface. Whereas, if the search only returned what was searched, that iteration and parsing would be unncessary 5. How would the customer like to achieve this? (List the functional requirements here) Add the ability to search for a specific interface on a hosts/<id>/interfaces API call 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. When a host has multiple interfaces defined, the search will only return the one(s) matching the query. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? No 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. 11. Would the customer be able to assist in testing this functionality if implemented? Yes
Created redmine issue https://projects.theforeman.org/issues/24798 from this bug
Upstream bug assigned to akarsale
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24798 has been resolved.
Reproduced with this setup : two fake interfaces with mac address aa:bb:cc:dd:ee:ff and aa:bb:cc:dd:ee:85 curl -k -u <user>:<password> https://<hostname>/api/hosts/5/interfaces?search=mac~aa:bb:cc:dd:ee:ff results for sat 6.7 output: { "total": 3, "subtotal": 1, "page": 1, "per_page": 20, "search": "mac~aa:bb:cc:dd:ee:ff", "sort": { "by": null, "order": null }, "results": # ommitted } and here I am searching for mac~aa:bb:cc:dd:ee curl -k -u <user>:<password> https://<hostname>/api/hosts/5/interfaces?search=mac~aa:bb:cc:dd:ee { "total": 3, "subtotal": 2, "page": 1, "per_page": 20, "search": "mac~aa:bb:cc:dd:ee", "sort": { "by": null, "order": null }, "results": # ommitted } I was able to reproduce the problem on sat 6.6 snap 24 same setup, curl -k -u <user>:<password> https://<hostname>/api/hosts/5/interfaces?search=mac~aa:bb:cc:dd:ee:ff { "total": 3, "subtotal": 3, "page": 1, "per_page": 20, "search": "mac~aa:bb:cc:dd:ee:ff", "sort": { "by": null, "order": null }, "result": # ommitted } Verified.
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-2020:1454