| Summary: | Virt-Who fails to register esx guests to satellite | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Freddy E. Montero <fmontero> |
| Component: | Usability | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED NOTABUG | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.2.0 | CC: | apitanga, bcourt, bkearney, fmontero, kabbott |
| Target Milestone: | Unspecified | Flags: | kabbott:
needinfo?
(bkearney) |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-23 19:59:12 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: | |
Looking at the included foreman-debug log Candlepin processed a report successfully and returned a mapping that appears to have 10 hypervisors and 121 guests successfully reported. |
Description of problem: Virt-Who doesn't register any vm guests running on esx hosts to the Satellite. Furthermore the hypervisors gets properly registered to Satellite but then there is no hypervisor to guest associations Version-Release number of selected component (if applicable): virt-who-0.17-9.el7sat How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Shouyld register guests to Satellite and associate guest to its parent hypervisor Expected results: Additional info: 2016-08-25 10:20:21,674 [virtwho.init DEBUG] MainProcess(38033):MainThread @executor.py:__init__:65 - Using config named 'VMLAB-B' 2016-08-25 10:20:21,674 [virtwho.init INFO] MainProcess(38033):MainThread @main.py:main:160 - Using configuration "VMLAB-B" ("esx" mode) 2016-08-25 10:20:21,674 [virtwho.init INFO] MainProcess(38033):MainThread @main.py:main:162 - Using reporter_id='lsalnymrhnap01' 2016-08-25 10:20:21,677 [virtwho.main DEBUG] MainProcess(38033):MainThread @executor.py:run:171 - Starting infinite loop with 3600 seconds interval 2016-08-25 10:20:21,722 [virtwho.VMLAB-B DEBUG] Esx-1(38044):MainThread @virt.py:run:364 - Virt backend 'VMLAB-B' started 2016-08-25 10:20:21,723 [virtwho.VMLAB-B DEBUG] Esx-1(38044):MainThread @esx.py:_prepare:128 - Log into ESX 2016-08-25 10:20:21,944 [virtwho.VMLAB-B DEBUG] Esx-1(38044):MainThread @esx.py:_prepare:131 - Creating ESX event filter 2016-08-25 10:20:22,656 [virtwho.VMLAB-B DEBUG] Esx-1(38044):MainThread @virt.py:enqueue:357 - Report for config "VMLAB-B" gathered, putting to queue for sending 2016-08-25 10:20:22,682 [virtwho.main DEBUG] MainProcess(38033):MainThread @subscriptionmanager.py:_connect:119 - Authenticating with RHSM username sa tadmin 2016-08-25 10:20:22,816 [virtwho.main DEBUG] MainProcess(38033):MainThread @subscriptionmanager.py:hypervisorCheckIn:171 - Checking if server has capa bility 'hypervisor_async' 2016-08-25 10:20:22,895 [virtwho.main DEBUG] MainProcess(38033):MainThread @subscriptionmanager.py:hypervisorCheckIn:183 - Server does not have 'hyper visors_async' capability 2016-08-25 10:20:22,900 [virtwho.main INFO] MainProcess(38033):MainThread @subscriptionmanager.py:hypervisorCheckIn:194 - Sending update in hosts-to-guests mapping for config "VMLAB-B": 8 hypervisors and 118 guests found 2016-08-25 10:20:22,904 [virtwho.main DEBUG] MainProcess(38033):MainThread @subscriptionmanager.py:hypervisorCheckIn:195 - Host-to-guest mapping: { "labxny005.VMLAB.network.com": [ { "guestId": "422eab76-85fe-b10d-7909-d1d820d9d3a0", "state": 5, "attributes": { "active": 0, "virtWhoType": "esx" } }, ... ... ... ...