Bug 1392704 - if add a invalid vdsm host to rhevm, virt-who will return error message due to the "NoneType" object.
Summary: if add a invalid vdsm host to rhevm, virt-who will return error message due ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.0
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: pre-dev-freeze
: ---
Assignee: Chris Snyder
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-08 03:33 UTC by Eko
Modified: 2020-12-11 11:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-11 11:17:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Comment 3 Chris Snyder 2016-12-22 16:59:55 UTC
We should give an appropriate error message.

Comment 4 yuefliu 2017-01-17 08:05:19 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.

Comment 7 Jan Kurik 2017-12-06 10:39:49 UTC
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/

Comment 10 Kevin Howell 2017-12-14 15:05:12 UTC
Can you please test if this an issue with the latest virt-who builds?

Comment 12 Rehana 2020-12-11 11:17:25 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.