Bug 836642

Summary: Plugin page displays blank chart and no workflow table
Product: [Fedora] Fedora Reporter: Brian Sipos <BSipos>
Component: trac-workflowadmin-pluginAssignee: Andrea Veri <andrea.veri>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17CC: andrea.veri, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 18:29:09 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:
Attachments:
Description Flags
A view of the web page in firefox none

Description Brian Sipos 2012-06-29 18:08:53 UTC
Created attachment 595347 [details]
A view of the web page in firefox

Description of problem:
The workflow plugin is able to be enabled and selected in the admin console, but no workflow data is displayed in either the table or the image, and any attempts to push buttons result in a Trac error.

Version-Release number of selected component (if applicable):
Plugin version 0.12.0.1, Trac version 0.12.3

How reproducible:
Every time on multiple Trac projects.

Steps to Reproduce:
1. Install the plugin package.
2. Open the admin console on a trac project.
3. Open the "Workflow Admin" admin section.
4. Observe the blank view, although a look at the underlying HTML seems to have table data (which must be hidden by javascript??).
  
Actual results:
A blank flow graph and no workflow stages.

Expected results:
A table with workflow stages and graph display of the same.

Additional info:
The back trace after pushing a button (in this case the "Move Up" button):
File "/usr/lib/python2.7/site-packages/trac/web/main.py", line 522, in _dispatch_request
  dispatcher.dispatch(req)
File "/usr/lib/python2.7/site-packages/trac/web/main.py", line 243, in dispatch
  resp = chosen_handler.process_request(req)
File "/usr/lib/python2.7/site-packages/trac/admin/web_ui.py", line 117, in process_request
  path_info)
File "/usr/lib/python2.7/site-packages/tracworkflowadmin/web_ui.py", line 90, in render_admin_panel
  self._parse_request(req)
File "/usr/lib/python2.7/site-packages/tracworkflowadmin/web_ui.py", line 405, in _parse_request
  params = json.loads(req.args.get('params'))
File "/usr/lib64/python2.7/json/__init__.py", line 326, in loads
  return _default_decoder.decode(s)
File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
  obj, end = self.raw_decode(s, idx=_w(s, 0).end())

I can also provide sections of the produced HTML for the page; there seems to be a table in the HTML but it is not displayed in the browser.

Comment 1 Andrea Veri 2012-06-30 15:59:52 UTC
Do you have the 'graphviz' package installed? If not, can you install it and report back please?

Comment 2 Brian Sipos 2012-07-02 12:29:40 UTC
Yes, I installed graphviz after I saw that there was a dependence on the graph tools. After installing graphviz, I have since restarted tracd several times, and always see the same workflow display.

Comment 3 Kevin Fenzi 2012-07-05 15:50:36 UTC
FYI, It seems to work just fine on RHEL6 where I did all my testing... so this would seem to me to be a python or other f17 related issue...

Comment 4 Fedora End Of Life 2013-07-03 19:40:17 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 5 Fedora End Of Life 2013-07-31 18:29:14 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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