#381: Bug and Update syncs shouldn't be halted by an isolated problem with one
update or bug
--------------------------------------+----------------------------------
Reporter: tflink | Owner: tflink
Type: enhancement | Status: new
Priority: major | Milestone: Undetermined Future
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+----------------------------------
= problem =
The current bug and update sync algorithms are very fragile in that one
error will stop the entire sync algorithm, leaving stuff out of sync with
bodhi or bugzilla. This has caused problems in the past
= analysis =
This could be solved by better error handling in the sync process such
that an error is logged but doesn't bubble up to the main sync code and
halt the entire process.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/381>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#384: Improve documentation
--------------------------------------+------------------------
Reporter: tflink | Owner: tflink
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 20
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+------------------------
= problem =
At the moment, our documentation is out of date and somewhat incomplete.
= analysis =
Update the docs and find an appropriate place for them to live.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/384>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#387: Updates pending stable show as stable
--------------------------------------+---------------------
Reporter: kparal | Owner: tflink
Type: defect | Status: new
Priority: minor | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
A package that is in updates-testing and is pending stable is shown as
[stable] in the app. That can cause some confusion (i.e. one of us can
close a related bug by assuming the package is already stable, and the
package push can be cancelled afterwards).
I think the app should display the repository the package is currently in,
not the repository the package in pending to. What do you think?
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/387>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#386: Update URLs should comtain the update ID when possible
--------------------------------------+----------------------------------
Reporter: tflink | Owner: tflink
Type: enhancement | Status: new
Priority: minor | Milestone: Undetermined Future
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+----------------------------------
= problem =
The update URLs fetched from bodhi are most reliable when they are based
off of the update ID which is generated when the update is pushed to
testing. However, the blocker tracking app generally grabs the URL before
this happens and thus, end up with the preliminary url based on update
contents.
= analysis =
The update sync process should look to replace any update URLs which are
not based on the update ID when the sync runs against bodhi.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/386>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#383: Migrate from FAS to FAS-OpenID
--------------------------------------+------------------------
Reporter: tflink | Owner: tflink
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 20
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+------------------------
= problem =
With the introduction of FAS-OpenID, the current method of FAS
authentication will be going away somewhere around F20. We will need to
migrate to the newer FAS-OpenID before that time.
= analysis =
The OpenID code in python-fedora-flask should make the transition
relatively painless but it will still require quite a bit of testing to
make sure that everything still works.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/383>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#367: Display flash messages in appropriate place
--------------------------------------+----------------------------------
Reporter: mkrizek | Owner: tflink
Type: enhancement | Status: new
Priority: minor | Milestone: Undetermined Future
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+----------------------------------
= problem =
Currently flash messages containing information for user are not
displayed.
= analysis =
There should probably be a box right under the header on all pages that
would display flash messages.
= enhancement recommendation =
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/367>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-tflink.rhcloud.com/r/23/
-----------------------------------------------------------
Review request for blockerbugs.
Bugs: 372
https://fedorahosted.org/fedora-qa/ticket/372
Repository: blockerbugs
Description
-------
This patch wraps bugzilla faults in a BugzillaError and prevents them from not being logged and generating http 500 server error.
Diffs
-----
blockerbugs/util/bz_interface.py 0579b2455b57a03e3bee570b8cd97aac0eeaf1a4
blockerbugs/controllers/main.py 6d32e5de91900cda33f5e0342c7854adb24fc8b6
Diff: http://reviewboard-tflink.rhcloud.com/r/23/diff/
Testing
-------
Thanks,
Martin Krizek
#372: Bugzilla Faults During Proposal are not logged, lead to http 500 errors
--------------------------------------+------------------------
Reporter: tflink | Owner: tflink
Type: defect | Status: new
Priority: critical | Milestone: Fedora 19
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+------------------------
= bug description =
When bugzilla faults during proposal don't have fault code 51, the
internal !BugzillaError class isn't used and the fault is lost when
attempting to extract information from it
{{{
[Wed Mar 27 13:26:38 2013] [error] [20130327-13:26PM] [blockerbugs]
[ERROR] Exception on /propose_bug [POST]
[Wed Mar 27 13:26:38 2013] [error] Traceback (most recent call last):
[Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site-
packages/flask/app.py", line 1687, in wsgi_app
[Wed Mar 27 13:26:38 2013] [error] response =
self.full_dispatch_request()
[Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site-
packages/flask/app.py", line 1360, in full_dispatch_request
[Wed Mar 27 13:26:38 2013] [error] rv = self.handle_user_exception(e)
[Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site-
packages/flask/app.py", line 1358, in full_dispatch_request
[Wed Mar 27 13:26:38 2013] [error] rv = self.dispatch_request()
[Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site-
packages/flask/app.py", line 1344, in dispatch_request
[Wed Mar 27 13:26:38 2013] [error] return
self.view_functions[rule.endpoint](**req.view_args)
[Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site-
packages/blockerbugs/controllers/users.py", line 84, in decorated_function
[Wed Mar 27 13:26:38 2013] [error] return f(*args, **kwargs)
[Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site-
packages/blockerbugs/controllers/main.py", line 375, in propose_bug
[Wed Mar 27 13:26:38 2013] [error] bugform.bugid.errors = [e.msg]
[Wed Mar 27 13:26:38 2013] [error] AttributeError: 'Fault' object has no
attribute 'msg'
}}}
= fix recommendation =
Either all of the bugzilla faults need to be wrapped in a !BugzillaError
or the error handling needs to be capable of handling multiple error
types.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/372>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance