#371: HTTP 500 after proposing a blocker bug
--------------------------------------+---------------------
Reporter: kparal | Owner: tflink
Type: defect | Status: new
Priority: major | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
I tried to propose https://bugzilla.redhat.com/show_bug.cgi?id=928339 as
an alpha blocker and I got HTTP 500 after submitting the form. The bug was
not proposed.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/371>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
This took a bit longer than I was hoping but we finally have a staging
instance of the new blocker tracking app up and running:
https://qa.stg.fedoraproject.org/blockerbugs/
There are still a few kinks to work out around syncing with bugzilla
and on the app administration side of things but it is ready for
testing.
This new version allows for blocker/FE proposal though the web
interface after logging in with your FAS id and password. The first
proposal will prompt you for your bugzilla credentials so that you will
be added to the cc list of any bug you propose but this will only
happen once (per database - this will be reset when the app moves to
production) and we don't store any password information.
Keep in mind that this is working against the PRODUCTION bugzilla for
now - any bugs which are proposed using the web interface will show up
as real blockers. Please don't propose blocker/FE bugs just to try
it out. Once partner-bugzilla is back up and running, the staging
instance will be more testable without affecting the regular processes.
If you hit any issues, please let me know or file a bug against the
blocker tracking app in the fedora-qa trac:
- https://fedorahosted.org/fedora-qa/newticket
Huge 'Thank You's to Martin Krizek for his help on the code, reviews and
testing and to Kevin Fenzi for his help and patience in getting the app
ready for staging deployment.
Tim
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-tflink.rhcloud.com/r/16/
-----------------------------------------------------------
Review request for blockerbugs.
Bugs: 337
https://fedorahosted.org/fedora-qa/ticket/337
Repository: blockerbugs
Description
-------
Initial packaging work and reworking all the various cli scripts into a single module to make it more packaging friendly
Diffs
-----
update_blockers.sh d5229ea9b54119608e73cabcabbaaf4d99248876
sync_db.py 3489434c9cd6dc4f67ad82f61b171f94c4d65793
setup.py b4a51dc9c4bb9dadbd5ada286b8ddd5448811886
run_cli.py PRE-CREATION
initialize.py eb3c3e160e66f5f044e20f53ff79994820fd4a7e
init_db.sh 540dcb1f4baff9d7d0cad0dc75d67a4d6f3c3a98
docs/source/installation.rst PRE-CREATION
docs/source/index.rst PRE-CREATION
docs/source/development.rst PRE-CREATION
docs/source/conf.py PRE-CREATION
docs/Makefile PRE-CREATION
doc/source/installation.rst 41319a6c345987bf50663ae4ff88068aed81334c
doc/source/index.rst f07f013268aaa01cec780efec6e320c6cb267339
doc/source/development.rst 35b1b34a6b81d8d35e91fb11d32b35dc5d8269a9
doc/source/conf.py fc14e55effbd22e0c2b4fef5c7a395d16f0a5f70
doc/Makefile 8c16a97606680359188461c22ef48777b5ee9ee0
blockerbugs/cli.py PRE-CREATION
blockerbugs/__init__.py 9030c04ee244ce21439075be9c446a83c05ed9ae
blockerbugs.spec PRE-CREATION
alembic.ini 848a3873008f231b03c12c4bcfe6d7367527f8fc
Diff: http://reviewboard-tflink.rhcloud.com/r/16/diff/
Testing
-------
I've done a bunch of local testing and have a staging instance set up in the cloud: https://209.132.184.164/blockerbugs/
Thanks,
Tim Flink