Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1551762

Summary: python2-virtualbmc reports type error upon every invocation.
Product: Red Hat OpenStack Reporter: Vincent S. Cojot <vcojot>
Component: python-virtualbmcAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: mlammon
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 12.0 (Pike)CC: bfournie, dtantsur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-12 15:06:15 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:

Description Vincent S. Cojot 2018-03-05 22:09:26 UTC 
Description of problem:

[raistlin@vkvm1 ~/virt-OSPD]$ sudo vbmc add overcloud-ceph-0 --port 6230
Exception TypeError: "'NoneType' object is not callable" in <function _removeHandlerRef at 0x1fe8de8> ignored

[raistlin@vkvm1 ~/virt-OSPD]$ sudo vbmc list
+------------------+--------+---------+------+
|   Domain name    | Status | Address | Port |
+------------------+--------+---------+------+
| overcloud-ceph-0 |  down  |    ::   | 6230 |
+------------------+--------+---------+------+
Exception TypeError: "'NoneType' object is not callable" in <function _removeHandlerRef at 0x1425de8> ignored


This is a fully patched RHEL7.4 KVM host upon which the following rpms were installed (taken from OSP-12):

python-virtualbmc-1.2.0-1.el7ost.noarch.rpm
python-pyghmi-1.0.22-1.el7ost.noarch.rpm
python2-pbr-3.1.1-2.el7ost.noarch.rpm
Comment 1 Bob Fournier 2018-03-12 15:06:15 UTC 
See explanation here for this issue - https://bugzilla.redhat.com/show_bug.cgi?id=1419723#c4

The message is a nuisance only and not a functional issue.  There is a fix in progress that will fix this message (among other things) so marking this as a duplicate.

*** This bug has been marked as a duplicate of bug 1473276 ***