jinja2 import error on container start

Bug #1532275 reported by Paul Bourke on 2016-01-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-mesos
High
Paul Bourke

Bug Description

This may well be a user error, but I've come across it now while trialing kolla-mesos on two separate setups.

General process (shown for just rabbitmq)

* Create fresh libvirt VM
* Install mesos/marathon/zookeeper/chronos as shown at https://open.mesosphere.com/getting-started/install/
* Clone kolla and kolla-mesos
* pip install both
* Build kolla images (tools/build.py --type source --base oraclelinux -i .buildconf -I .runconf rabbitmq)
* kolla-mesos-deploy

rabbitmq task can be seen in the marathon UI (along with others which I wouldnt expect to start as I only built rabbitmq), in state TASK_FAILED, with message " Docker container run error: Container exited on error: exited with status 1"

Checking the docker logs on the failed container show the following:

[root@node01 kolla-mesos]# docker logs b2cff8f232b4
sudo: unable to send audit message: Operation not permitted
INFO:__main__:Kolla config strategy set to: COPY_ONCE
INFO:__main__:Validating config file
INFO:__main__:Copying service configuration files
INFO:__main__:Copying /kolla/config/mariadb/mariadb/kolla_mesos_start.py to /usr/local/bin/kolla_mesos_start
INFO:__main__:Setting permissions for /usr/local/bin/kolla_mesos_start
INFO:__main__:Writing out command to execute
Running command: 'kolla_mesos_start'
Traceback (most recent call last):
  File "/usr/local/bin/kolla_mesos_start", line 30, in <module>
    import jinja2
ImportError: No module named jinja2

I haven't dug into the kolla_mesos_start script yet, but it seems the images are missing jinja2. Has anyone else encountered this?

Changed in kolla-mesos:
importance: Undecided → High
assignee: nobody → Paul Bourke (pauldbourke)
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers