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:
rhevh in vlan cannot show up in rhevm, getVdsCaps returns unexpected error.


Version-Release number of selected component (if applicable):
rhev-hypervisor-6.2-0.11.el6

How reproducible:
Always.

Steps to reproduce:
1. Configure network with vlan_id=20 and network interface is up.
2. Register to rhevm.
3. Approve host in rhevm.

Actual results:
rhevh failed to show up in rhevm, getVdsCaps returns unexpected error.

Expected results:
rhevh show up in rhevm. 

Additional info:
After approve the host in rhevm, rhevh host display some error on screen and must be ended by Crtl + C and can continue. see screenshot.

Created attachment 517394 [details]
logs and screenshots

mark testblocker as if the host cannot show up in vlan will block other testings in vlan.

Re-test on the same build (6.2-0.11), cannot reproduce. Hence close this as not a Bug.