Bug 890486

Summary:	virsh domif-getlink command fail with '--config' option
Product:	Red Hat Enterprise Linux 7	Reporter:	yanbing du <ydu>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	acathrow, dyasny, dyuan, jyang, mzhan, rwu, whuang
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	890483	Environment:
Last Closed:	2012-12-28 05:07:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description yanbing du 2012-12-27 08:33:41 UTC

+++ 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:

Comment 2 Osier Yang 2012-12-28 04:31:30 UTC

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.

Comment 3 yanbing du 2012-12-28 05:07:30 UTC

(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.