Remove-ContainerNetwork hangs after reboot
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
Undecided
|
Dariusz Sosnowski | |||
OpenContrail |
Fix Committed
|
Undecided
|
Dariusz Sosnowski |
Bug Description
When there is a container running, compute node reboot breaks the HNS and container networks cannot be removed.
Bug was found during the vRouter development.
Steps to reproduce:
1. Create a network named `network1` in Contrail controller.
2. Deploy Contrail Windows Compute Node.
3. Disable automatic startup of Contrail Windows services.
3. Create a Docker network assigned to Contrail network:
docker network create -d Contrail --ipam-driver windows --opt tenant=admin --opt network=network1
4. Start a container in this network:
docker run -id --network network1 microsoft/
5. Stop the compute node:
6. Power on the compute node.
7. Start Docker and clean up containers.
8. Stop Docker.
9. Attempt to clear up container networks
What should happen:
1. Remove-
What happens:
1. Remove-
Other symptoms of the bug:
- after the reboot, `Get-VMSwitch | Get-VMSwitchExt
Id : 56553588-
Name : vRouter forwarding extension
Vendor : OpenContrail team
Version : 23.29.23.449
SwitchId : 464d0af9-
SwitchName : Layered Ethernet1
Enabled : True
Running : False
CimSession : CimSession: .
IsDeleted : False
- kernel debugger reports that the VMSwitch protocol drivers failed to bind the adapter (accessible through `!vswitch` WinDbg command):
VSWITCH ffffba815fa48000
Name: 714626e9-
vPort List: Count (1)
Type Address Id Type IsValidation MonitorMode FriendlyName
VPORT ffffba815fa45000 0x0000 Default N None Layered Ethernet1
description: | updated |
Changed in opencontrail: | |
status: | New → Fix Committed |
Review in progress for https:/ /review. opencontrail. org/47862
Submitter: Dariusz Sosnowski (<email address hidden>)