Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Bug 1382901

Summary:	Virt-who document bug in section- 5.5
Product:	Red Hat Satellite	Reporter:	rakesh kumar <rakumar>
Component:	Docs Virtual Instances Guide	Assignee:	Russell Dickenson <rdickens>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Stephen Wadeley <swadeley>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	adahms, pmutha, swadeley
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-14 00:12:19 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 rakesh kumar 2016-10-08 07:37:05 UTC

Document URL: https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/virtual-instances-guide/

Section Number and Name: 5.5. CONFIGURING VIRT-WHO TO CONNECT TO VMWARE VCENTER

Describe the issue: - Account name by which virt-who is to connect to the hypervisor. If a Microsoft Windows domain account is being used, the format for the username option must be domain_name\\account_name. Note the use of two backslashes.

For the username, it says to use 

username=corporate\\svc-virt-who

but that does not work in the /etc/virt-who.d/* configs.  The double backslash is for the /etc/sysconfig/virt-who file.  The virt-who.d configs should be a single backslash.  This is mentioned in https://access.redhat.com/solutions/1270223 and https://access.redhat.com/solutions/1424003

Suggestions for improvement: 

Format should be: 
username=corporate\svc-virt-who

Additional information:

Comment 3 Stephen Wadeley 2016-10-12 14:48:55 UTC

Section 5.2

Virt-who Configuration Files

mentions /etc/sysconfig/virt-who, but does not mention `username`


Russell wanted to make another improvement using UPN format name.

I will assign to Russell.

By the way, I see typo: and and

Comment 4 Andrew Dahms 2016-10-13 00:07:42 UTC

Setting release flags.

Comment 7 Russell Dickenson 2016-10-14 00:12:19 UTC

As the changes for this BZ ticket are complete, and the updated Virtual Instances Guide published to the Customer Portal [1], I have closed this BZ ticket.

The convention for KBase links is being discussed elsewhere.


[1] https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/virtual-instances-guide/#configuring_virt_who_to_connect_to_vmware_vcenter