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.
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
Description of problem: running virt-who with "--hyperv" option by CLI, and then set other options to other modes, such as "--esx-owner, --esx-env, --esx-server, --esx-username, --esx-password", virt-who still can work, that means it will not check all the parameters consistency. Version-Release number of selected component (if applicable): virt-who-0.18-1.el6.noarch subscription-manager-1.18.5-1.el6.x86_64 python-rhsm-1.18.5-1.el6.x86_64 How reproducible: always Steps to Reproduce: 1. run virt-who with an wrong parameter, such as "--hyperv" with "--esx-owner, --esx-env, --esx-server, --esx-username, --esx-password": # virt-who --hyperv --esx-owner=Default_Organization --esx-env=Library --esx-server=10.73.5.208 --esx-username=Administrator --esx-password=Welcome1 -d -o 2016-12-13 01:14:08,564 [virtwho.init INFO] MainProcess(7100):MainThread @main.py:main:165 - Using configuration "env/cmdline" ("hyperv" mode) 2016-12-13 01:14:08,564 [virtwho.init INFO] MainProcess(7100):MainThread @main.py:main:167 - Using reporter_id='hp-z220-07.qe.lab.eng.nay.redhat.com' 2016-12-13 01:14:08,593 [virtwho.env_cmdline DEBUG] MainProcess(7100):MainThread @hyperv.py:__init__:472 - Hyper-V url: http://10.73.5.208:5985/wsman 2016-12-13 01:14:08,595 [virtwho.env_cmdline DEBUG] HyperV-1(7107):MainThread @virt.py:run:363 - Virt backend 'env/cmdline' started 2016-12-13 01:14:08,609 [virtwho.env_cmdline DEBUG] HyperV-1(7107):MainThread @hyperv.py:retry_ntlm_negotiate:64 - Using NTLM authentication 2016-12-13 01:14:08,613 [virtwho.env_cmdline DEBUG] HyperV-1(7107):MainThread @hyperv.py:retry_ntlm_authenticate:77 - Sending NTLM authentication data 2016-12-13 01:14:08,737 [virtwho.env_cmdline DEBUG] HyperV-1(7107):MainThread @hyperv.py:retry_ntlm_authenticate:100 - NTLM authentication successful 2016-12-13 01:14:08,739 [virtwho.env_cmdline DEBUG] HyperV-1(7107):MainThread @hyperv.py:getHostGuestMapping:521 - Unable to enumerate using root/virtualization namespace, trying root/virtualization/v2 namespace 2016-12-13 01:14:11,670 [virtwho.env_cmdline DEBUG] HyperV-1(7107):MainThread @virt.py:enqueue:356 - Report for config "env/cmdline" gathered, putting to queue for sending 2016-12-13 01:14:11,671 [virtwho.env_cmdline DEBUG] HyperV-1(7107):MainThread @virt.py:run:384 - Virt backend 'env/cmdline' stopped after sending one report 2016-12-13 01:14:11,676 [rhsm.https DEBUG] MainProcess(7100):MainThread @https.py:<module>:59 - Using m2crypto wrappers to provide httplib and ssl 2016-12-13 01:14:11,683 [rhsm.connection INFO] MainProcess(7100):MainThread @connection.py:__init__:758 - Connection built: host=bootp-73-3-220.eng.pek2.redhat.com port=443 handler=/rhsm auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=0 2016-12-13 01:14:11,684 [rhsm.connection DEBUG] MainProcess(7100):MainThread @connection.py:_request:490 - Making request: GET /rhsm/status/ 2016-12-13 01:14:11,682 [virtwho.main DEBUG] MainProcess(7100):MainThread @subscriptionmanager.py:_connect:124 - Authenticating with certificate: /etc/pki/consumer/cert.pem 2016-12-13 01:14:11,857 [rhsm.connection INFO] MainProcess(7100):MainThread @connection.py:_request:525 - Response: status=200, request="GET /rhsm/status/" 2016-12-13 01:14:11,857 [rhsm.connection DEBUG] MainProcess(7100):MainThread @connection.py:_request:490 - Making request: GET /rhsm/status 2016-12-13 01:14:11,857 [virtwho.main DEBUG] MainProcess(7100):MainThread @subscriptionmanager.py:hypervisorCheckIn:172 - Checking if server has capability 'hypervisor_async' 2016-12-13 01:14:12,035 [rhsm.connection INFO] MainProcess(7100):MainThread @connection.py:_request:525 - Response: status=200, request="GET /rhsm/status" 2016-12-13 01:14:12,036 [rhsm.connection DEBUG] MainProcess(7100):MainThread @connection.py:_load_manager_capabilities:803 - Server has the following capabilities: ['cores', 'ram', 'instance_multiplier', 'derived_product', 'cert_v3', 'guest_limit', 'vcpu', 'storage_band'] 2016-12-13 01:14:12,037 [rhsm.connection DEBUG] MainProcess(7100):MainThread @connection.py:_request:490 - Making request: POST /rhsm/hypervisors?owner=Default_Organization&env=Library 2016-12-13 01:14:12,036 [virtwho.main DEBUG] MainProcess(7100):MainThread @subscriptionmanager.py:hypervisorCheckIn:184 - Server does not have 'hypervisors_async' capability 2016-12-13 01:14:12,036 [virtwho.main INFO] MainProcess(7100):MainThread @subscriptionmanager.py:hypervisorCheckIn:195 - Sending update in hosts-to-guests mapping for config "env/cmdline": 1 hypervisors and 1 guests found 2016-12-13 01:14:12,036 [virtwho.main DEBUG] MainProcess(7100):MainThread @subscriptionmanager.py:hypervisorCheckIn:196 - Host-to-guest mapping: { "564D1925-0DE4-4E14-8B73-2A2444FB15A3": [ { "guestId": "A9BB7EA8-5CC7-CF46-B5D2-6C8FFE6EE3A6", "state": 1, "attributes": { "active": 1, "virtWhoType": "hyperv" } } ] } 2016-12-13 01:14:13,368 [rhsm.connection INFO] MainProcess(7100):MainThread @connection.py:_request:525 - Response: status=200, request="POST /rhsm/hypervisors?owner=Default_Organization&env=Library" 2016-12-13 01:14:13,368 [virtwho.main DEBUG] MainProcess(7100):MainThread @executor.py:send_report:102 - Report for config "env/cmdline" sent 2016-12-13 01:14:13,369 [virtwho.main DEBUG] MainProcess(7100):MainThread @__main__.py:main:23 - virt-who terminated 2016-12-13 01:14:13,370 [virtwho.main DEBUG] MainProcess(7100):MainThread @executor.py:terminate:308 - virt-who is shutting down Actual results: virt-who only check "--hyperv" parameter, ignore to check other parameters are matched or not. Expected results: virt-who should check all the parameter consistency