Hide Forgot
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:
This issue is addressed upstream and will be fixed by virt-who rebase.
Fixed in virt-who-0.17-1.el7.
Verified in virt-who-0.17-1.el7 # grep "encryped" /etc/virt-who.d/template.conf # grep "encrypted" /etc/virt-who.d/template.conf template.conf:#encrypted_password= ; password encrypted using virt-who-password utility template.conf:#encrypted_password=
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