Hide Forgot
Description of problem: The network device with vlan setting display "disabled" instead of "dhcp" on TUI Version-Release number of selected component (if applicable): rhev-hypervisor6-6.2-20120119.1.el6_2 How reproducible: 100% Steps to Reproduce: 1. TUI install RHEV-H in vlan ENV. 2. Set network to DHCP with correct vlan ID (e.g. 20). 3. Focus on Network detail page. Actual results: Network configuration can successful, but network device shows "Disable" instead of "DHCP". Expected results: The network device can make the right choices. Additional info:
Created attachment 556474 [details] vlan
http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=commit;h=d52a050b01d7f0a74697188e3c051dbd9562b31b
Test version: rhev-hypervisor6-6.3-20120215.0.el6 Steps to Reproduce: 1. TUI install RHEV-H in vlan ENV. 2. Set network to DHCP with correct vlan ID (e.g. 20). 3. Focus on Network detail page. Test result: Network configuration successful, network device shows dhcp. So the bug is fixed, change bug status to VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously, in a vlan environment, the TUI would show a network device as "disabled". It will now correctly show the status of the network device.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Previously, in a vlan environment, the TUI would show a network device as "disabled". It will now correctly show the status of the network device.+Previously, in a VLAN environment, the text user interface incorrectly displayed network devices as "disabled". The interface has been updated and now correctly displays the actual status of the network device.
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. http://rhn.redhat.com/errata/RHBA-2012-0741.html