| Summary: | if add a invalid vdsm host to rhevm, virt-who will return error message due to the "NoneType" object. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Eko <hsun> |
| Component: | virt-who | Assignee: | Chris Snyder <csnyder> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Eko <hsun> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | hsun, khowell, redakkan, sgao, yuefliu |
| Target Milestone: | pre-dev-freeze | Keywords: | Reopened |
| Target Release: | --- | ||
| 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-12-11 11:17:25 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: | |
|
Comment 3
Chris Snyder
2016-12-22 16:59:55 UTC
1. When add a valid vdsm host to rhevm, virt-who also feedback the "'NoneType' object has no attribute 'text'" error during the host installing process, and after host add successfully, virt-who will send host/guest mapping info normally. 2. When the virt-who is getting and sending the host/guest mapping info normally for rhevm mode, if we add/delete/pause/resume/poweron/poweroff a guest, virt-who will fail to sent report with error message - "Unable to send data: Communication with subscription manager failed with code 500: undefined local variable or method `hypervisor' for #<Class:0x00000006be4118>". And after the trigger option for the guest complete, virt-who will be back to normal and send mapping info successfully. Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/ Can you please test if this an issue with the latest virt-who builds? Old bug clean up : ================ Closing the bug with Current release ,the bug was verified by QE during a RHEL release cycle but was not closed. |