Bug 1409849 - UI: Storage domains not showing in search on a DC named with an underscore
Summary: UI: Storage domains not showing in search on a DC named with an underscore
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium with 1 vote
Target Milestone: ovirt-4.1.2
: 4.1.2
Assignee: Ravi Nori
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
: 1418924 1419334 1436378 1437520 1449350 (view as bug list)
Depends On:
Blocks: 1436378
TreeView+ depends on / blocked
 
Reported: 2017-01-03 15:55 UTC by Fred Rolland
Modified: 2020-11-14 04:56 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-05-23 08:13:32 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+
mgoldboi: planning_ack+
mperina: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 69926 0 master MERGED core : Storage domains not showing in search on a DC named with an underscore 2017-01-15 11:54:42 UTC
oVirt gerrit 74977 0 ovirt-engine-4.1 MERGED core : Storage domains not showing in search on a DC named with an underscore 2017-03-31 16:41:36 UTC
oVirt gerrit 77204 0 master MERGED search: fix tags/values with underscore behaviour 2017-05-25 14:26:06 UTC
oVirt gerrit 77484 0 ovirt-engine-4.1 MERGED search: fix tags/values with underscore behaviour 2017-05-29 11:51:03 UTC

Description Fred Rolland 2017-01-03 15:55:31 UTC
Description of problem:
The storage domains are not showing in the "Storage" tab

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Create a data center with an underscore in the name (e.g: 4_1)
2.Add an host + a storage domain
3. Select the data center on the left tree, and select the "Storage" tab

Actual results:
No storage domains in the list

Expected results:
The storage domain appears in the list

Additional info:

The issue is in the SQL query, a back slash is added before the underscore:

SELECT * FROM ((SELECT distinct storage_domains_for_search.* FROM  storage_domains_for_search   WHERE '4\_1' ILIKE ANY(string_to_array(storage_domains_for_search.storage_pool_name::text, ',')))  ORDER BY storage_name ASC ) as T1 OFFSET (1 -1) LIMIT 100

Comment 2 Tal Nisan 2017-02-07 10:44:28 UTC
*** Bug 1419334 has been marked as a duplicate of this bug. ***

Comment 3 Tal Nisan 2017-02-07 16:30:19 UTC
*** Bug 1418924 has been marked as a duplicate of this bug. ***

Comment 4 Allon Mureinik 2017-03-30 15:21:54 UTC
Martin - please see bug 1436378.
If Maor's analysis is correct there, I think this BZ needs to retargeted for 4.1.z.

Comment 5 Martin Perina 2017-03-30 15:46:50 UTC
(In reply to Allon Mureinik from comment #4)
> Martin - please see bug 1436378.
> If Maor's analysis is correct there, I think this BZ needs to retargeted for
> 4.1.z.

No problem, fix is not that complicated, moving to 4.1.2

Comment 6 Allon Mureinik 2017-03-30 16:21:38 UTC
*** Bug 1437520 has been marked as a duplicate of this bug. ***

Comment 7 Csiga 2017-03-31 10:01:30 UTC
Dear Support,

I'm waiting for the 4.1.2 release.

Thank you foir your help!

Best Regards,
Csiga

Comment 8 Maor 2017-04-05 15:46:17 UTC
*** Bug 1436378 has been marked as a duplicate of this bug. ***

Comment 9 Thijs Braem 2017-04-07 08:37:45 UTC
Hi oVirt people. 

Just wanted to add that I'm patiently waiting for this fix as well. The bug affects foreman usability as well: it's no longer possible to create new VM's from within foreman if DC has an underscore in it. 

So thanks for moving it to 4.1.2! If any workaround is possible, it would be very nice to know as well.

Comment 10 Lucie Leistnerova 2017-05-03 07:29:52 UTC
Storages from left menu on DC with underscore are displayed.

verified in ovirt-engine-4.1.2-0.1.el7.noarch

Comment 11 Tal Nisan 2017-05-11 16:08:17 UTC
*** Bug 1449350 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.