Module lxc_container uses wrong path to lxc-create on CentOS

[Johannes Kastl]

Dear List,

is it just on my machine that the lxc_container module uses the wrong
path to lxc-create?

> fatal: [xyz]: FAILED! => {"changed": false, "command": "/bin/lxc-create --name foobar --quiet --template download --bdev btrfs -- -d centos -r 7 -a amd64", "err": "", "failed": true, "msg": "Failed executing lxc-create.", "rc": 1}

This is a CentOS7 host running lxc 2.0. Both lxc and python2-lxc are
installed as packages, that I built myself
(https://build.opensuse.org/project/monitor/home:ojkastl_buildservice:LXC_Vanilla_stable-2.0).

I do not know if this error is in my copy of the python bindings, but
a short grep did not show anything.

As this is a community module, I'll have to find out where to report
bugs. If this is a bug...

Johannes

[Johannes Kastl]

On 28.01.17 16:35 Johannes Kastl wrote:

>> fatal: [xyz]: FAILED! => {"changed": false, "command": "/bin/lxc-create --name foobar --quiet --template download --bdev btrfs -- -d centos -r 7 -a amd64", "err": "", "failed": true, "msg": "Failed executing lxc-create.", "rc": 1}

Hmm, I should read the error messages more exact. lxc-create actually
is in /bin/lxc-create.

Off investigating.

Johannes

[Johannes Kastl]

On 28.01.17 16:37 Johannes Kastl wrote:

> Hmm, I should read the error messages more exact. lxc-create
> actually is in /bin/lxc-create.

Sorry, my fault. One ansible statement did not work the way I wanted
and lxc-create did not like the btrfs parameter when not being run on
a btrfs...

Johannes