Devstack runs failing due to "Failure creating NET_ID for 36033ee931044cb5bc76570da0eff97b"

Bug #1265904 reported by Ben Nemec
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Incomplete
Undecided
Unassigned
devstack
Invalid
Undecided
Unassigned

Bug Description

This problem has popped up on a number of changes recently. Devstack fails to complete successfully so the change fails without ever running any tests.

Example error.txt: http://logs.openstack.org/37/61037/9/check/check-tempest-dsvm-neutron/6d98c79/logs/error.txt.gz

Tags: gate-failure
Revision history for this message
Matt Riedemann (mriedem) wrote :
Changed in openstack-ci:
status: New → Confirmed
tags: added: gate-failure
Revision history for this message
Matt Riedemann (mriedem) wrote :

Doesn't look like logs/error.txt.gz is indexed so I'm not sure what we can key off of for an elastic-recheck query.

Revision history for this message
Matt Riedemann (mriedem) wrote :

I opened bug 1265906 for indexing on logs/error.txt.gz since we'd need that to query against this failure it seems.

Clark Boylan (cboylan)
Changed in openstack-ci:
status: Confirmed → Incomplete
Revision history for this message
Matt Riedemann (mriedem) wrote :

I'm not seeing anything jump out at me from the recent neutron commit history, but there are a few in the recent devstack commit history that make me wonder about regressions:

https://review.openstack.org/61854
https://review.openstack.org/63493
https://review.openstack.org/62306
https://review.openstack.org/63641

Given the timing, the first one seems to be the most suspicious.

Revision history for this message
Ben Nemec (bnemec) wrote :

Looks like this is probably caused by https://bugs.launchpad.net/python-neutronclient/+bug/1265926 A fix (https://review.openstack.org/#/c/64910/) is in the gate waiting to be merged. Going to close this bug for now, will reopen if that doesn't fix the problem.

Changed in devstack:
status: New → Invalid
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

I think rather than close the bug, it should be marked as a duplicate. Doing so.

Revision history for this message
Steve Martinelli (stevemar) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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