container connect both bridge and kuryr network in CI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-libnetwork |
Fix Released
|
Medium
|
Liping Mao |
Bug Description
Currently, in CI test, we use the following way to create container:
docker_
docker_client.start
docker_
We did not pass network_config when create_container, this will cause the container use default bridge for network, then we add kuryr network into the container, the container will have two interface(one is bridge, another one is kuryr). This is not what we want.
According to dockerpy doc:
https:/
It need to be changed to when create the container assign kuryr network to it.
something like:
network_
docker_
docker_client.start
Changed in kuryr-libnetwork: | |
assignee: | nobody → Liping Mao (limao) |
summary: |
- container connect both bridge and kuryr network in fullstack/rally test - case + container connect both bridge and kuryr network in CI |
description: | updated |
Changed in kuryr-libnetwork: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. openstack. org/396048
Review: https:/