freezer doesn't work when deployed

Bug #1830540 reported by Marek Grudzinski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
High
Marek Grudzinski
Train
Fix Released
High
Marek Grudzinski
Ussuri
Fix Released
High
Marek Grudzinski

Bug Description

Deploying freezer out of the box expects elasticsearch 2.3.0 (according to freezer docs)
Kolla-ansible deploys elasticsearch with 5.6.x
Due to this freezer is deployed onto elasticsearch 5.6.x it won't work since it uses older query types.

Freezer could be used with mariadb/mysql instead. It would be more suitable for an out-of-the-box solution for kolla-ansible and let users to deploy it towards elasticsearch with options, even if its the better option (scalability).

I'm not sure that deploying a secondary elasticsearch (in kolla-ansible) out-of-the-box just for freezer is suitable, but also an option.

Revision history for this message
Marek Grudzinski (ivve) wrote :

I'll submit a change to use the existing mariadb as default with options to point out an external (compatible) elasticsearch.

Changed in kolla-ansible:
assignee: nobody → Marek Grudzinski (ivve)
Revision history for this message
Marek Grudzinski (ivve) wrote :

Here is the fresh proposal: https://review.opendev.org/661485

Mark Goddard (mgoddard)
Changed in kolla-ansible:
status: New → In Progress
importance: Undecided → High
Revision history for this message
BN (zatoichy) wrote :

Do you have any errors related to freezer on horizon UI? When I am trying to open it - Error: [*] Error 500: search operation failed: TransportError(400, u'parsing_exception', u'no [query] registered for [filtered]')

Mark Goddard (mgoddard)
Changed in kolla-ansible:
milestone: 10.0.0 → none
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.