Bug 1436378 - After upgrade to 4.1.1 attached storage domains don't appear in the API
Summary: After upgrade to 4.1.1 attached storage domains don't appear in the API
Keywords:
Status: CLOSED DUPLICATE of bug 1409849
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.1.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.1.2
: ---
Assignee: Maor
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On: 1409849
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-27 19:27 UTC by Juan Hernández
Modified: 2017-04-05 15:46 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-04-05 15:46:17 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.1+


Attachments (Terms of Use)

Description Juan Hernández 2017-03-27 19:27:01 UTC
After upgrade to version 4.1.1 of the engine, the following query no longer returns the storage domains that are attached to a data center:

  GET /ovirt-engine/api/storagedomains?search=+datacenter%3D%22mydc%22

This is the query sent by Foreman to find the storage domains.

Comment 1 Yamakasi 2017-03-27 19:49:34 UTC
I have discussed this with Juan and we figure out it happened on my upgrade from:

4.0.6 to 4.1.1

The same Foreman version (1.14.2) was working good on oVirt 4.0.6 so I doubt if this is an issue on the Foreman side.

I can see if I can so some tests for some log output but there are no errors here during the API calls.

Comment 3 Allon Mureinik 2017-03-28 07:22:31 UTC
Juan - is this an infrastructural issue, or something the Storage team shoudl take?

Comment 4 Juan Hernández 2017-03-28 07:52:00 UTC
Allon, I don't know yet. If someone in your team has an upgraded/upgradable environment where to test this then I would appreciate if you can take it, as otherwise it will take a long time for me to make that environment to check it.

I verified with the reporter that the data center name was correct, and that it didn't appear in the result of the search query. But other than that I didn't do any analysis yet.

Comment 5 Allon Mureinik 2017-03-29 08:22:17 UTC
I can't reproduce this.
Going through the commit history I can't see anything related, but we need to check deeper.
We'll take the lead, and in the worst case, if we find an infra issue, we'll move it back there.

Maor, can you take a look please?

Comment 6 Yaniv Lavi 2017-03-29 14:26:57 UTC
Can you please add the engine logs from the problematic environment?

Comment 7 Maor 2017-03-29 16:21:34 UTC
I've queries the reporter DB and it seems to work well, it could not reproduced on my env.

Yamakasi, 
Does other search queries using DC name works? (For example from VMs)
What about search other attributes instead of DC?

Is there any chance to look into the engine Host or use it.

Comment 8 Yamakasi 2017-03-29 17:52:58 UTC
Moar as discussed on IRC, PM me there so we can update this BZ

Comment 9 Allon Mureinik 2017-03-30 12:43:21 UTC
I'm pushing this out to 4.1.2 ATM (so 4.1.1 can be pushed forwards), as it doesn't reproduce in the general case.

Comment 10 Maor 2017-03-30 15:18:37 UTC
The problem is with the underscore of the DC name.
The DC name of the reporter contains underscore which makes the search look for 'AMS-01\_STRING-01\_STRING' instead of 'AMS-01_STRING-01_STRING'
There is already an open bug on that in:
https://bugzilla.redhat.com/1409849

Yamakasi, can you please build oVirt with https://gerrit.ovirt.org/#/c/69926/
and see if that fixes the problem?

Comment 11 Yamakasi 2017-03-30 15:47:19 UTC
Hi Moar,

I saw your message on IRC, thanks great progress!

I need to find out if I can build it, I never builded it before myself.

Comment 12 Maor 2017-03-31 09:42:26 UTC
Actually, you can simply change the DC name to be without underscore and check if the search works.
If it does, I think it is safe to close this bug as duplicate of BZ1409849

Comment 13 Yamakasi 2017-04-05 15:02:51 UTC
This is indeed temporary fixed with replacing the underscore with a dash. I think I created a duplicate as described above.

Comment 14 Maor 2017-04-05 15:46:17 UTC
Thanks for the update Yamakasi, closing this as dup

*** This bug has been marked as a duplicate of bug 1409849 ***


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