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.

Created attachment 530402 [details]
vdsm-reg.log

Description of problem:
Approval of RHEV-H hosts fail due to an inability to change the name of the breth0 bridge to rhevm.

Version-Release number of selected component (if applicable):
vdsm-4.9-110

How reproducible:
Always

Steps to Reproduce:
1.Install RHEV-H
2.Add to rhev-m either through RHEV-M Add Host or through RHEV-H TUI
3.
  
Actual results:
if RHEV-M add host, sits in pending when it should auto-approve
if rhev-h tui, then fails to ever show up in rhev-m

Expected results:
add is completed successfully

Additional info:

MainThread::ERROR::2011-10-26 23:08:23,219::deployUtil::785::root::makeBridge found existing bridge named: breth4

shows up only if fIsBridgeDevice and not fIsOvirt.

Could it be that os.path.exists('/etc/rhev-hypervisor-release') returns false?

Yes, it does it does.  Rename from rhev-hypervisor to rhev-hypervisor6 had the unintended consequence of changing the file to /etc/rhev-hypervisor6-release.  

Moving to rhev-hypervisor6 component to be fixed.

*** This bug has been marked as a duplicate of bug 748005 ***