Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The network device of bonding display "disabled" instead of "dhcp" on TUI.
#cat ifcfg-brbond4
DEVICE=brbond4
ONBOOT=yes
BOOTPROTO=dhcp
TYPE=Bridge
Version-Release number of selected component (if applicable):
rhev-hypervisor-6.2-0.17.2
How reproducible:
Always.
Steps to reproduce:
1. Configure nic bonding with two nics using mode 4.
2. Restart network service. #need to change "networking=yes" in /etc/sysconfig/network.
3. Exit and Check status page.
Actual results:
The network device of bonding display "disabled" status .
Expected results:
The network device of bonding display dhcp or static accordingly.
If you login again separately (with ssh) or reboot and login, does this still show up?
Joey, might be related to bug 740127 that's already fixed but not in the build yet.
(In reply to comment #3)
> If you login again separately (with ssh) or reboot and login, does this still
> show up?
>
login with ssh or reboot, it shows up.
Meet this issue on rhevh-6.2-20111026.2 again, login with ssh or reboot, the rhevm over bond4 always displayed "disable" status, but this time I was creating the bonding network via RHEV-M.