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.

Description of problem:
When using the virt who-configuration tool, the configuration script will fail to parse the username field properly when the username is a Windows Domain user and starts with a '$' as follows:

domain\$atellite


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

Satellite 6.3.1

How reproducible:

Repeatable

Steps to Reproduce:
1. Execute the virt-who configuration utility
2. Enter username domain\$atellite
3. Execute script output on the Satellite

Actual results:
User name is mangled and the password is encrypted incorrectly.

Expected results:
username is stored properly and password is retrievable via hash.

Additional info:
The user name may be manually input and configured and the password hashed via virt-who-password and this configuration will work.

Created redmine issue http://projects.theforeman.org/issues/23638 from this bug

Verified in Satellite 6.4 Snap 9

I followed the reporter's reproduction steps.

Resulting config is:
/etc/virt-who.d/virt-who-config-1.conf

### This configuration file is managed via the virt-who configure plugin
### manual edits will be deleted.
[virt-who-config-1]
type=esx
hypervisor_id=hostname
owner=Default_Organization
env=Library
server=test.server.com
username=domain\$atellite
encrypted_password=f931434859f3ea195b6ef6303d5a809b
rhsm_hostname=<my.sat.domain.com>
rhsm_username=virt_who_reporter_1
rhsm_encrypted_password=4def7ba2155a8f6eebde0c6650aaad5e7f9d5bf8762b6d66890620384a0d515a
rhsm_prefix=/rhsm

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927