networking-midonet

v2 job failure with "IP address 172.19.0.1 already allocated in subnet b27eec93-1648-4695-892c-f93feea43107"

Bug #1683233 reported by YAMAMOTO Takashi
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
networking-midonet
Won't Fix
Critical
YAMAMOTO Takashi
networking-midonet 5.0.0

Bug Description

eg. http://logs.openstack.org/34/429434/1/gate/gate-tempest-dsvm-networking-midonet-v2-ubuntu-xenial/193fa9c/logs/devstacklog.txt.gz

2017-04-17 05:11:06.688 | +++ /opt/stack/new/networking-midonet/devstack/uplink/create_uplink.sh:source:121 : openstack --os-project-name admin port create --network mn-uplink-net --host ubuntu-xenial-osic-cloud1-s3700-8440549 --binding-profile interface_name=mn-uplink-virt --fixed-ip ip-address=172.19.0.1 --fixed-ip ip-address=fd1a:6fd3:0a22::1 mn-uplink-port
2017-04-17 05:11:59.847 | HttpException: Conflict (HTTP 409) (Request-ID: req-fd9e6f27-2305-410e-aefb-9a1a1fbf9f2f), IP address 172.19.0.1 already allocated in subnet b27eec93-1648-4695-892c-f93feea43107

Tags: gate-failure
YAMAMOTO Takashi (yamamoto)
Changed in networking-midonet:
importance: Undecided → Critical
milestone: none → 5.0.0
tags: added: gate-failure
Revision history for this message
Antonio Ojea (aojea) wrote :

is this bug still valid?

Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

i haven't seen it lately.

Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

i haven't seen this recently. and v2 plugin has been removed.

Changed in networking-midonet:
assignee: nobody → YAMAMOTO Takashi (yamamoto)
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.