Inconsistency description of "br-ext"

Bug #1657637 reported by Dongfeng Huang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tricircle
Fix Released
Low
Dongfeng Huang

Bug Description

In the document networking-prerequisites.rst, the description of "br-etx" should be "br-ext". It occurred only in one place.

The document link is:
https://github.com/openstack/tricircle/blob/master/doc/source/networking-prerequisites.rst

The error location is:
Using following command to connect the bridge to physical ethernet interface, as shown below, "br-vlan" is wired to eth1, and "br-etx" to eth2.

Changed in tricircle:
assignee: nobody → Dongfeng Huang (southeast02)
Chaoyi Huang (joehuang)
Changed in tricircle:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tricircle (master)

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

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

Reviewed: https://review.openstack.org/422431
Committed: https://git.openstack.org/cgit/openstack/tricircle/commit/?id=a55fee6e31704b995916faed0c8274ead8d3b8b8
Submitter: Jenkins
Branch: master

commit a55fee6e31704b995916faed0c8274ead8d3b8b8
Author: Dongfeng Huang <email address hidden>
Date: Thu Jan 19 15:30:03 2017 +0800

    "br-etx" should be "br-ext" in the doc

    1. What is the problem?
    In the document networking-prerequisites.rst, the "br-ext" is
    written as "br-etx". It should be "br-ext".

    2. What is the solution to the problem?
    Change the description of "br-etx" to "br-ext".

    3. What the features need to be implemented to the Tricircle to realize
    the solution?
    No new features.

    Change-Id: I57c3f55f1ed07a6328a1af96459364df224551b8
    Closes-Bug: #1657637

Changed in tricircle:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tricircle 3.0.0

This issue was fixed in the openstack/tricircle 3.0.0 release.

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.