Bug 1416298
Summary: | Virt-who report wrong guests status for hyper-v when configure guests with same guest name | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Liushihui <shihliu> | ||||||
Component: | virt-who | Assignee: | William Poteat <wpoteat> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 7.3 | CC: | bbuckingham, hsun, jcallaha, jhnidek, khowell, sgao, tomckay, toneata, wpoteat, yuefliu | ||||||
Target Milestone: | alpha | Keywords: | Triaged | ||||||
Target Release: | 7.7 | ||||||||
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: | 2020-03-31 19:08:44 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: | |||||||||
Attachments: |
|
Description
Liushihui
2017-01-25 08:16:48 UTC
Created attachment 1244191 [details]
import_process1
Created attachment 1244192 [details]
import_success
Moving component to upstream virt-who (seems like a general virt-who issue). Why is this a valid test? It is not sustainable to create more than one guest vm with the same guest id. When you make the duplicate, change the system uuid and check the outcome. Can you give me the connection information to the hyperv manager so I can see what state is getting sent? The log also if you can capture it. Workaround: The state of the systems is stored in a hash table by "ElementName". That is the system name "7.6_Server_x86_64". It will only keep the state it gets last and use it for all systems with that name. Rename the systems to be unique. I will examine the collected data to see if there is a field that will always be unique for this purpose. 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-2020:0990 |