DragonFlow

tap-metadata exists that cause metadata service start failure

Bug #1656500 reported by Li Ma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DragonFlow
Fix Released
Medium
Li Ma

Bug Description

The tap-metadata exists in the system. The metadata service will not set up ip correctly in this situation. It causes service startup failure.

Li Ma (nick-ma-z)
Changed in dragonflow:
importance: Undecided → Medium
assignee: nobody → Li Ma (nick-ma-z)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to dragonflow (master)

Fix proposed to branch: master
Review: https://review.openstack.org/420306

Changed in dragonflow:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to dragonflow (master)

Reviewed: https://review.openstack.org/420306
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=fe8bc32be90f0c2b27cf69b2805cce211b8f8c94
Submitter: Jenkins
Branch: master

commit fe8bc32be90f0c2b27cf69b2805cce211b8f8c94
Author: Li Ma <email address hidden>
Date: Sat Jan 14 15:23:38 2017 +0800

    Delete the tap-metadata device when it exists in the system

    The existing tap-metadata device causes failure of service
    startup. We first check its existance and re-initialize the
    environment when necessary.

    Change-Id: I9d6f1262909ee461e5891a023f7394565a12f91b
    Closes-Bug: #1656500

Changed in dragonflow:
status: In Progress → Fix Released
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.