Bug 1569299
| Summary: | Failed to get mapping info - virt-who - KeyError: 'config.network.dnsConfig.hostName' | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Waldirio M Pinheiro <wpinheir> | |
| Component: | virt-who | Assignee: | William Poteat <wpoteat> | |
| Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.5 | CC: | aeladawy, ahumbe, asakpal, csnyder, dbragalo, dnunes, khowell, ktordeur, mharris, patalber, rajukuma, rraghuwa, salmy, wpoteat, yuefliu | |
| Target Milestone: | pre-dev-freeze | Keywords: | Triaged, ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1573172 (view as bug list) | Environment: | ||
| Last Closed: | 2018-10-30 10:47:49 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: | 1573172 | |||
Given that we would like to handle by being more resilient in virt-who, changing product/component commit ec5e88d635d882a5d4a9b350ab5b5e1e93cb6782 Business justification (customer impact; how would the defect impact customers’ business? why is it not possible to wait for a fix in Y-Stream?): The defect causes ESX host reporting to fail. If any of the hosts in the network are missing the unique id as configured in the virt-who installation, then none of those hosts are reported to the server. In this scenario, the host/guest mappings are not captured and host-dependent subscriptions cannot be assigned to the guests. The Y-stream for 7.6 is not set to release until October. How many customers are impacted by this defect? The bugzilla for this has 6 customer issues attached. Any customer using VMWare, VSphere, or ESX may be affected. When was the defect introduced in this major version of RHEL? Is it a regression? This was introduced between 7.4 and 7.5 and it is a regression. What is the minimal patch set to fix this bug? (link, git commit,...) https://github.com/candlepin/virt-who/pull/138/commits/ec5e88d635d882a5d4a9b350ab5b5e1e93cb6782 Please refer to the 7.5-z bug for the resolution in 7.5 https://bugzilla.redhat.com/show_bug.cgi?id=1573172 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:3169 |
Description of problem: Some customers are facing issue when virt-who is trying to retrieve the vCenter information. In all cases the issue started without any change/update on Satellite / Packages / Configuration side. Version-Release number of selected component (if applicable): virt-who-0.21.5-1.el7.noarch How reproducible: only on customer env. I'm trying to reproduce inhouse but without success. Steps to Reproduce: 1. 2. 3. Actual results: --- 2018-04-18 08:38:07,747 [virtwho.main ERROR] MainProcess(6836):Thread-2 @virt.py:run:388 - Thread 'virt-who-config-3' fails with exception: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 379, in run self._run() File "/usr/lib/python2.7/site-packages/virtwho/virt/esx/esx.py", line 215, in _run assoc = self.getHostGuestMapping() File "/usr/lib/python2.7/site-packages/virtwho/virt/esx/esx.py", line 262, in getHostGuestMapping uuid = host['config.network.dnsConfig.hostName'] KeyError: 'config.network.dnsConfig.hostName' --- Expected results: No issues, virt-who collecting data normally from vCenter side. Additional info: