Project

General

Profile

Bug #26004

virt-who does not match all guest virtual machines on the ESXi hypervisor

Added by Ludwig Bayerlein 8 months ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Hi,

we are using virt-who in our environment with the latest version installed.

Versions

Katello: 3.8.1
virt-who: 0.22.5-1
Foreman: 1.19.1

virt-who asks the vCenter server for its virtual machines on one esxi. The esxi answers with 1 hypervisors und 51 machines. One of the virtual machines is t-wmu70, which is reported correctly. The hypervisor (esxi) is listed in content hosts via "virt-who-vmu147-5" with 25 content hosts. Unfortunately, t-wmu70 is not listed as virtual machine for this hypervisor. But we have proven it und registered it correctly via subscription-management. Bot systems (virtual machine and virt-who server) are RedHat systems.

Now why is t-wmu70 not a content host running on virt-who-vmu147-5?

I tried this change, but without success: https://github.com/Katello/katello/pull/7817/files

2019-02-06_15-30.png View 2019-02-06_15-30.png 66.3 KB Ludwig Bayerlein, 02/06/2019 02:54 PM
2019-02-06_15-29.png View 2019-02-06_15-29.png 58 KB Ludwig Bayerlein, 02/06/2019 02:54 PM
2019-02-06_15-28.png View 2019-02-06_15-28.png 76.9 KB Ludwig Bayerlein, 02/06/2019 02:54 PM
virt-who-debug.txt virt-who-debug.txt 25.7 KB Ludwig Bayerlein, 02/06/2019 03:01 PM
2019-02-06_15-31.png View 2019-02-06_15-31.png 95.4 KB Ludwig Bayerlein, 02/06/2019 03:08 PM
2019 02 06 15 30 2019 02 06 15 29 2019 02 06 15 28 2019 02 06 15 31

History

#1 Updated by Ludwig Bayerlein 8 months ago

Attached virt-who debug log

#2 Updated by Ludwig Bayerlein 8 months ago

  • Description updated (diff)

#3 Updated by Ludwig Bayerlein 8 months ago

  • File deleted (2019-02-06_15-31.png)

#5 Updated by Ludwig Bayerlein 7 months ago

  • Found in Releases Katello 3.11.0 added

I did an upgrade of our machine to Katello version 3.11 RC2 (katello-3.11.0-0.1.rc2.el7.noarch) and it is the same behaviour. Following knowledgebase is successfully tested and the problem still exists: https://access.redhat.com/solutions/1592573

  • The VDC is assigned to the hypervisor (status is fully entitled)
  • The client is subscribed via subscriptionmanager
  • The virt-who debug log tells me the right UUID from the client (tested from this KB article: https://access.redhat.com/solutions/3068371)
  • The virt-who client successfully connects to the esxi/vcenter
  • The virt-who client successfully connects to the rhsm
  • The rhsm does not show me any errors
  • The virt-who service is running

After unsubscribing the missing virtual machine and resubscribing again, following message comes up in the Foreman gui: Red Hat Enterprise Linux Server: Not supported by a valid subscription.
On the client (virtual machine), I get following message, after trigger a "subscription manager status"
-----------------------------------------
System Status Details
-----------------------------------------
Overall Status: Invalid

If I assign the VDC manually, the Foreman gui tells me, that its partially subscribed, but not reported by anyone.

We will do a rollback to version 3.8.1 again, because all date were shown as invalid instead of the real date.

#6 Updated by Chris Roberts 7 months ago

  • Triaged changed from No to Yes

#7 Updated by Chris Roberts 7 months ago

  • Triaged changed from Yes to No

#8 Updated by Andrew Kofink 7 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello Backlog

#9 Updated by Ludwig Bayerlein 6 months ago

I have got an update and there are no good news for debugging purposes.

We did a migration on our infrastructure and changed the ESXi hypervisors. The old ones run out of support and has been replaced by new ones. Now after this migration, the virt-who configuration works again and resolves near 100% of all hosts. Except of two unimportant virtual machines, every other has the correct match to its hypervisor and vice verca. I really don't know what happened, but we cannot debug it any more, except of the two non working machines.

If I can provide more informations, please tell me how to support.

Also available in: Atom PDF