zaqar container wrong configuration

Bug #1647831 reported by Eduardo Gonzalez on 2016-12-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eduardo Gonzalez

Bug Description

This bug is part of a rework of zaqar to make it functional, some other issues may be added into this bud_id while developing Ansible roles and finding other issues in the process.

- zaqar-manage command does not exist in zaqar.
- /var/log/kolla not created on
- pymongo package missing in source install.
- unify homedir under /var/lib/zaqar in a single command.

description: updated
Changed in kolla:
milestone: none → ocata-2
importance: Undecided → Medium
Changed in kolla:
milestone: ocata-2 → ocata-3

Submitter: Jenkins
Branch: master

commit 69e2e9fff15ea9d20d81426cf384fe85177fb69b
Author: Eduardo Gonzalez <email address hidden>
Date: Tue Dec 6 19:51:11 2016 +0000

    Fix zaqar container

    This PS is part of a rework on zaqar container.
    In it's current state is not working in kolla.
    Will be adding/fixing issues under this PS.

    - Remove bootstrap zaqar:
      At this point zaqar-manage command does not exist.
      Boostraping is not needed while starting zaqar container.

    - Add pymongo package in source install.

    - Create /var/log/kolla folder.

    - Change zaqar homedir to /var/lib/zaqar and unify creation.

    - Zaqar's source default have config files as *.sample.
      Policy.json need to be present if keystone auth
      is going to be used.

    - Zaqar uses wsgi to the API, heka decoder need to be added

    Change-Id: I9c6716b64345d9e846902ffbfbf033135e3eabd9
    Closes-Bug: #1647831

Changed in kolla:
status: In Progress → Fix Released

This issue was fixed in the openstack/kolla development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers