Description of problem:
When jboss-as with ovirt-optimizer is listening on incorrect address ui-plugin of optimizer shows "Status: Data refresh failed: 0".
This status may come up any time optimizer is not accepting packets from ui-plugin machine.
First I though that 0 is a counter of how many refresh interval ui-plugin failed to load data. Unfortunately it's just a simple zero :(
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start ovirt-optimizer in jboss
2. Start ovirt-optimizer-ui-plugin on engine
3. Configure jboss to listen only on localhost
4. See the status
Status: Data refresh failed: 0
At least delete the ": 0". From the end. I would prefer to give admin some kind of informative message. "Failed to send data to ovirt-optimizer" or something similiar.
Just a cosmetic change I don't think it needs any logs. If necessary I'll add them.
It it the HTTP status that was returned with the failed call. 0 means there was no connection. If you configure the ui plugin to talk to some arbitrary web server, you will get others.. 404 for not found, 403 for prohibited
(In reply to Martin Sivák from comment #1)
> It it the HTTP status that was returned with the failed call. 0 means there
> was no connection. If you configure the ui plugin to talk to some arbitrary
> web server, you will get others.. 404 for not found, 403 for prohibited
Worth adding a status indication (all good / cannot connect to server)?
*** Bug 1156122 has been marked as a duplicate of this bug. ***
verified on : Red Hat Enterprise Virtualization Manager Version: 3.6.0-0.18.el6
If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format:
The documentation team will review, edit, and approve the text.
If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
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.