Red Hat Bugzilla – Bug 989419
Bond0 generated automatically when only create Bond[1-9]
Last modified: 2014-09-24 11:09:51 EDT
+++ This bug was initially created as a clone of Bug #987840 +++
Description of problem:
When only create bond[1-9], bond0 will generated automatically. And the bond0 will be misunderstanding because it has no member. So should not generated bond0 in TUI.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Clear install ovirt-node
2. Create bond1.
3. Check in TUI.
In step3, bond0 generated automatically. And bond0 can be configured as well.
It should not let bond0 display in TUI and not allow it to be configured.
Created attachment 779698 [details]
after create bond1
This issue can be reproduced on the fellow bulid:
So need to clone it from ovirt-node upstream to downstream to track this issue.
1. Clear install rhevh-6.5-20131024.1.0.iso.
2. Create bond2.
3. Check in TUI.
1.It only create bond2 in TUI.
This bug is fixed in rhevh-6.5-20131024.1.0.iso. So I will change the status from ON_QA to VERIFIED.
*** Bug 1008796 has been marked as a duplicate of this bug. ***
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thank you for your help.
Hi, could you give me a quick synopsis of this bug, cause, how it was fixed, for the doctext? Thanks.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.