Zun

failed to create container due to neutron network updation

Bug #1879671 reported by feng.shengqin@zte.com.cn on 2020-05-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zun
High
feng.shengqin@zte.com.cn

Bug Description

Docker internal error: 500 Server Error: Internal Server Error ("Invalid address 173.0.0.163: It does not belong to any of this network's subnets").

reproducte the error:
1.precreate a neutron network
2.preadd a subnet to neutron network
3.create a container
4.docker net created on a compute_node base on neutron network
5.add a new subnet to neutron network
6.create other container

Changed in zun:
assignee: nobody → feng.shengqin@zte.com.cn (feng-shengqin)
hongbin (hongbin034) on 2020-05-20
Changed in zun:
status: New → Confirmed
importance: Undecided → High
hongbin (hongbin034) wrote :

Given the limitation of the libnetwork model, it is impossible to fix this issue unless we move away from libnetwork and switch over to another network model (i.e. CNI).

Create a BP for the switch over to CNI: https://blueprints.launchpad.net/zun/+spec/migrate-docker-to-cni

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers