Check docker subnet is same with neutron subnet when kuryr use existed neutron network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-libnetwork |
New
|
Undecided
|
Unassigned |
Bug Description
When user create kuryr network with existed neutron network, if he assign subnet range not same with neutron subnet.
we get the following error message:
Error response from daemon: NetworkDriver.
Neutron server returns request_ids: ['req-9d364ebf-
But the kuryr.net.uuid.lh and kuryr.net.uuid.uh tag on neutron network is still leave there.
example:
+------
| Field | Value |
+------
| admin_state_up | True |
| availability_
| availability_zones | nova |
| created_at | 2016-12-02T04:08:27 |
| description | |
| id | 5b231d26-
| ipv4_address_scope | |
| ipv6_address_scope | |
| mtu | 1500 |
| name | provider-880 |
| port_security_
| provider:
| provider:
| provider:
| qos_policy_id | |
| router:external | False |
| shared | True |
| status | ACTIVE |
| subnets | 3ed277c0-
| tags | kuryr.net.
| | kuryr.net.
| | kuryr.net.
| | kuryr.net.existing |
| | kuryr.net.
| | kuryr.net.
| | kuryr.net.
| | kuryr.net.
| | kuryr.net.
| | kuryr.net.
| | kuryr.net.
| | kuryr.net.
| | kuryr.net.
| tenant_id | 0da303c4058e438
| updated_at | 2016-12-02T04:08:27 |
+------
This is because when user did not assign network uuid or network name, in vm nested case
summary: |
- create network failed in nested vm case + Check docker subnet is same with neutron subnet when kuryr use existed + neutron network |
description: | updated |
description: | updated |
This bug will also impact vm nest case, when user create a kuryr network. vm-nested driver will choose the network of the vm by default if end user did not assign neutron network uuid or name, then it will go into this bug also.