Description of problem - Provide a detailed description of the issue encountered, including logs/command-output snippets and screenshots if the issue is observed in the UI:
When an unexpected user input is sent to the filter VMs option on the Virtual machines page under Infrastructure of the RHACM hub console, the page results in SQLSTATE 42703 error.
This happens because in addition to allow the selection of dropdown items, user can also type in it and then click enter. This error is seen 4 out of 5 times.
The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI):
VMware
The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):
Internal/Converged
The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):
ACM 2.14.0-DOWNSTREAM-2025-04-21-05-11-18 ODF 4.19.0-58.stable OCP 4.19.0-0.nightly-2025-05-04-082442 GitOps 1.16.0 Submariner 0.20.0 Virt 4.19.0.141 OADP 1.4.4 MCE 2.9.0-212
Does this issue impact your ability to continue to work with the product?
Not really
Is there any workaround available to the best of your knowledge?
No
Can this issue be reproduced? If so, please provide the hit rate
Yes, 80%
Can this issue be reproduced from the UI?
Yes
If this is a regression, please provide more details to justify this:
Steps to Reproduce:
1. On a 4.19 Regional DR setup, deploy discovered app VM via CLI on any of the managed ODF cluster which is imported to the RHACM hub.
2. Check under Infrastructure -> Virtual machines of the RHACM hub console, wait and refresh the page until the workload appears on it.
3. In the filter VirtualMachines search bar, type a random text such as namespace of the workload, or any random text instead of selecting the dropdown options, and then press enter.
You are expected to see the SQLSTATE 42703 error. Try it 4-5 times.
The exact date and time when the issue was observed, including timezone details:
Actual results: [RDR] Unexpected user input into filter VirtualMachines results in SQLSTATE 42703 error
Refer attached screencast.
Expected results: This test case should be handled properly without throwing SQLSTATE 42703 error{}
Logs collected and log location:
Additional info: