Bug 852902 - Reserve workflow does not work until piwik js has finished loading
Summary: Reserve workflow does not work until piwik js has finished loading
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-29 22:57 UTC by Dan Callaghan
Modified: 2019-05-22 13:42 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-10-11 23:50:21 UTC
Embargoed:


Attachments (Terms of Use)

Description Dan Callaghan 2012-08-29 22:57:53 UTC
Description of problem:

If the Beaker site is configured to use a Piwik analytics server, the reserve workflow page will be non-functional until the request for piwik.js is completed. That means if the Piwik server is misbehaving, responding slowly, having an outage, unreachable, etc then it could make the reserve workflow page unusable.

This problem probably applies to any other page which has scripts waiting for the document ready event.

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

How reproducible:
easily

Steps to Reproduce:
1. Add an iptables rule to DROP traffic to your configured Piwik server:
# iptables -A OUTPUT -d analytics.example.com -j DROP
2. Visit the reserve workflow page
  
Actual results:
Ajaxy bits do not work. Changing any of the filters has no effect and no distros or distro trees will be populated. The page is unusable.

Expected results:
Loading of piwik.js should not hold up the rest of the page.

Comment 1 Dan Callaghan 2012-09-05 02:56:45 UTC
On Gerrit: http://gerrit.beaker-project.org/1319

Comment 3 Dan Callaghan 2012-10-11 23:50:21 UTC
Beaker 0.9.4 has been released.


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