Bug 1122035 - Inconsistent LMIIndicationListener API documentation (or broken API)
Summary: Inconsistent LMIIndicationListener API documentation (or broken API)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: openlmi-tools
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hatina
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-22 12:01 UTC by Alois Mahdal
Modified: 2015-06-30 01:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 01:29:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alois Mahdal 2014-07-22 12:01:16 UTC
Description of problem:
LMIIndicationListener constructor claims, but does not accept hostname.  In other words, when you call `help(LMIIndicationListener)`, you will be told that it takes hostname, port, certfile and keyfile, but when called with any of those parameters, it will complain that it only takes 1 parameter (self).

As a result, it is not possible to set listener hostname, certfile and keyfile (it is possible to set port in `start()`).

Version-Release number of selected component (if applicable):
commit ecefb90

How reproducible:
always (with custom git-based build)

Steps to Reproduce:
1. install OpenLMI
2. build openlmi-tools from ecefb90
3. start lmishell
4. `LMIIndicationLIstener('localhost')`

Actual results:
TypeError

Expected results:
listener instance

Additional info:
Even if only looking at the API docs (docstrings), it seems kind of inconsistent: For example, at the same time you can set port in constructor, but then you must override it when calling `start()`

Comment 1 Peter Hatina 2014-07-24 08:43:01 UTC
openlmi-tools; commit a3a73f0 should fix the compatibility issue.

it is necessary to install lmiwbem:
- from git or,
- lmiwbem-0.2.0-8.fc20

Comment 2 Fedora End Of Life 2015-05-29 12:26:10 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-30 01:29:31 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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