Docker/HNS networks are misconfigured after Windows reboots
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
Undecided
|
Unassigned | |||
OpenContrail |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
Due to network handling logic in Docker on Windows, restart of Docker service causes networks assigned to Contrail CNM plugin to change its driver from 'Contrail' to 'transparent. These networks cannot be used to run containers in Contrail.
Steps to reproduce:
1. Deploy Contrail Windows compute node.
2. Create a Docker network with Contrail driver on the compute node.
PS C:\> docker network create -d Contrail --ipam-driver windows --opt tenant=admin --opt network=mynetwork mynetwork
3. Inspect docker networks"
PS C:\> docker network ls
NETWORK ID NAME DRIVER SCOPE
3. Restart Docker service.
4. Inspect docker networks:
PS C:\> docker network ls
What should happen:
1. mynetwork should have Contrail driver assigned.
a9c68bd1b66d mynetwork Contrail local
What happens:
1. mynetwork is deleted and Docker reports internal HNS network corresponding to mynetwork:
5e51f3198de0 Contrail:
Changed in opencontrail: | |
status: | New → Fix Committed |
Review in progress for https:/ /review. opencontrail. org/47814
Submitter: Dariusz Sosnowski (<email address hidden>)