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.

+++ This bug was initially created as a clone of Bug #890483 +++
On rhel7 host can also reproduce this bug:
libvirt-1.0.1-1.el7.x86_64

Description of problem:
With --config option, virsh domif-getlink command always fail. 

Version-Release number of selected component (if applicable):
libvirt-0.10.2-13.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.
# virsh domiflist tt
Interface  Type       Source     Model       MAC
-------------------------------------------------------
vnet2      network    default    -           52:54:00:89:165

# virsh domif-getlink tt vnet2
vnet2 default

# virsh domif-getlink tt vnet2 --config
error: Interface (target: vnet2) not found.
2.
3.
  
Actual results:
as step1

Expected results:
--config option can work

Additional info:

I don't think this is a bug, because the vnet2 you used is generated
automatically by libvirt for a active domain if you don't specify it
explicitly. For an inactive domain, it doesn't exist if you don't specify
it. And the error reflects the truth.

(In reply to comment #2)
> I don't think this is a bug, because the vnet2 you used is generated
> automatically by libvirt for a active domain if you don't specify it
> explicitly. For an inactive domain, it doesn't exist if you don't specify
> it. And the error reflects the truth.

Get it, close it as NOTABUG.