Bug 1357761
Summary: | Problem with virt-who using Unicode characters in a hypervisor's account password? | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Sandeep <snikam> | |
Component: | virt-who | Assignee: | Jiri Hnidek <jhnidek> | |
Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> | |
Severity: | medium | Docs Contact: | ||
Priority: | high | |||
Version: | 6.7 | CC: | csnyder, jhnidek, rbalakri, rjerrido, snikam, yuefliu | |
Target Milestone: | rc | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1503271 (view as bug list) | Environment: | ||
Last Closed: | 2018-06-19 05:21:42 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1461138, 1503271, 1506745 |
Description
Sandeep
2016-07-19 05:59:15 UTC
The configuration in /etc/virt-who.d/ should work with unicode characters, but make sure the file is in UTF-8 encoding (e.g. using `file` command). The error "Reporting of hypervisor bsaz-zhru-pvh03.belsoftnet.local is not implemented in esx backend" is caused by invalid option in the `hypervisor_id` config. One of "uuid", "hwuuid", or "hostname" literals should be used instead of putting the hostname there directly. Let me know if this solves the issue. Thank you for your update. I will check the same with the customer and get back to you. Sandeep, do you have any update from the customer? The behaviour appears to have changed in newer versions of virt-who. In newer versions a traceback is printed to stdout, the result of an InvalidOption exception with the message "Option 'password' is not in latin1 encoding". I still believe this to be an issue. As the customer issue has been closed I am clearing needinfo on Sandeep. I can't reproduce this bug, but I can see following message many times in output of strace command in current master branch: stat("/etc/sysconfig/64bit_strstr_via_64bit_strstr_sse2_unaligned", 0x7ffdda271bd0) = -1 ENOENT (No such file or directory) It is also possible to reproduce this bug, when you simply set following environment variables: export VIRTWHO_ESX_SERVER=myvcenter.mydomain.local export VIRTWHO_ESX=1 export VIRTWHO_ESX_ENV=Library export VIRTWHO_ESX_OWNER=0000000 export VIRTWHO_ESX_USERNAME=service_account_id@MSDOMAIN export VIRTWHO_ESX_PASSWORD=1€345678 Then it is possible to run virt-who from local installation using: ./virt-who -o -d, because /etc/sysconfig/virt-who is read, when virt-who is installed in system (bash script virt-who-initscript). The fix has been merged to upstream virt-who. The fix should be included in the rebase on upstream for 6.10. As such I'm moving this bug to the MODIFIED state. 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/RHBA-2018:1915 |