Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
There is a type in the automatically generated template.conf file for virt-who
~~~
#encrypted_password vs #encryped_password
~~~
Version-Release number of selected component (if applicable):
# rpm -qa | grep virt-who
~~~
virt-who-0.14-9.el7.noarch
~~~
Actual results:
# cat /etc/virt-who.d/template.conf
~~~
## This is a template for virt-who configuration files. Please see
## virt-who-config(5) manual page for detailed information.
##
## virt-who checks all files in /etc/virt-who.d/ if they're valid ini-like
## files and uses them as configuration. Each file might contain more configs.
##
## You can uncomment and fill following template or create new file with
## similar content.
#[config name]
#type= ; insert one of libvirt/esx/hyperv/rhevm/vdsm/fake
#server= ; insert hostname or ip address of the server to connect to
#username= ; username for server authentication
#password= ; password for server authentication
#encryped_password= ; password encrypted using virt-who-password utility
#owner= ; owner for use with SAM, Customer Portal, or Satellite 6
#env= ; environment for use with SAM, Customer Portal, or Satellite 6
#hypervisor_id= ; how will be the hypervisor identified, one of: uuid, hostname, hwuuid
## For complete list of options, see virt-who-config(5) manual page.
## Terse version of the config template:
#[config name]
#type=
#server=
#username=
#password=
#encryped_password=
#owner=
#env=
#hypervisor_id=
~~~
Expected results:
~~~
## This is a template for virt-who configuration files. Please see
## virt-who-config(5) manual page for detailed information.
##
## virt-who checks all files in /etc/virt-who.d/ if they're valid ini-like
## files and uses them as configuration. Each file might contain more configs.
##
## You can uncomment and fill following template or create new file with
## similar content.
#[config name]
#type= ; insert one of libvirt/esx/hyperv/rhevm/vdsm/fake
#server= ; insert hostname or ip address of the server to connect to
#username= ; username for server authentication
#password= ; password for server authentication
#encrypted_password= ; password encrypted using virt-who-password utility
#owner= ; owner for use with SAM, Customer Portal, or Satellite 6
#env= ; environment for use with SAM, Customer Portal, or Satellite 6
#hypervisor_id= ; how will be the hypervisor identified, one of: uuid, hostname, hwuuid
## For complete list of options, see virt-who-config(5) manual page.
## Terse version of the config template:
#[config name]
#type=
#server=
#username=
#password=
#encrypted_password=
#owner=
#env=
#hypervisor_id=
~~~
Additional info:
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://rhn.redhat.com/errata/RHBA-2016-2387.html