Test failures in docker container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Slawek Kaplonski |
Bug Description
There are no enough resources to create the pool of virtual machines sometimes. People use containers in this case.
There are two tests that fail in docker container:
http://
The main reason is that docker container is not a Virtual Machine, so it doesn't provide all of the architecture in the same way that a Virtual Machine might. The underlying infrastructure of docker containers is configured on the Host system, not within the container itself
These tests use brctl and sysctl. You can use --privileged flag ('docker run' command) for brctl. What about sysctl? You can use sysctl commands with docker-client. But you can not use it inside a container.
It would be very cool if the tests were fixed so that they work in docker containers.
description: | updated |
Changed in neutron: | |
assignee: | nobody → Antonio Ojea (itsuugo) |
status: | New → In Progress |
Changed in neutron: | |
assignee: | Antonio Ojea (itsuugo) → Slawek Kaplonski (slaweq) |
tags: | added: neutron-proactive-backport-potential |
tags: | added: neutron-easy-proactive-backport-potential |
Do you have an example of the Dockerfile you are using to run these tests?