Bug 1650660
| Summary: | Race Condition: Previous search completions wipes out in progress search | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Bryan Kearney <bkearney> |
| Component: | Search | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Omkar Khatavkar <okhatavk> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.3.0 | CC: | bkearney, katello-qa-list, kgaikwad, mhulan, rohoover, satellite6-bugs, sgraessl, smutkule |
| Target Milestone: | Unspecified | Keywords: | Triaged, UserExperience |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1614906 | Environment: | |
| Last Closed: | 2021-01-19 21:33:31 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: | |||
| Bug Depends On: | 1614906 | ||
| Bug Blocks: | 1650655, 1650656 | ||
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in approximately a month. If you have any concerns about this, please contact your Red Hat Account team. Thank you. Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact your Red Hat Account Team. Thank you. |
Tracking this part - When updating the search parameters while a search is in process, the current behavior triggers on the completion of the search - which wipes out the updated search parameters. Worse, this definitely happens when performing the initial "empty" search. That is, when you go to a page and start definining a search, it will wipe out the search criteria. And if you successfully run a search before the "empty" search completes, you instead get the initial results and not your customized results. (I preseume the search was still submitted and created load on the system, although you will never be able to see the output.)