#436: SSH access to systems in Beaker lab
--------------------------------------+---------------------
Reporter: atodorov | Owner: tflink
Type: defect | Status: new
Priority: major | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
= bug description =
Currently systems in Beaker lab can be accessed only through bastion.fp.o
which is not as convenient as direct SSH into the system.
There's also the question whether or not to open the systems directly to
the Internet.
This needs to be discussed with infra. Filing here so it doesn't get lost.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/436>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#437: Need to import daily Fedora snapshots into Beaker
--------------------------------------+---------------------
Reporter: atodorov | Owner: tflink
Type: task | Status: new
Priority: major | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
= bug description =
In order to perform any meaningfull testing Beaker needs to import more
recent Fedora trees. It could be daily(nightly) snapshots or less often
depending on available resources.
The tree directory structure needs to be a copy/snapshot of the current
state at the time of import. The reason is b/c devel trees utilize one URL
but the contents under this URL are updated in a rolling fashion. We need
tree URLs where content is not changing in order to produce consistent
test results.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/437>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#433: blocker proposal form forgets everything after login timeout
--------------------------------------+---------------------
Reporter: kvolny | Owner: tflink
Type: defect | Status: new
Priority: major | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
= bug description =
I was trying to propose a F20 blocker. I needed to gather information from
multiple bugs, so it took me longer to write the justification. After
finishing and submitting that, I was presented with a login screen. After
logging in again, I was redirected to the proposal form again, but it was
completely empty, all the text that took me so long to write was gone.
(Okay, I'm a smart guy and I had it in clipboard for such case, but if I
had forgotten ... booh.)
= bug analysis =
Seems the login code doesn't care about other variables in the http
request ...
= fix recommendation =
1) If there is such a short login timeout, the user should be warned about
it (e.g. countdown timer on the page) and the page should allow refresh
without submitting the data.
2) Once the login expires, the submitted data should be caried over all
the redirects back to the submission form.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/433>
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/37/
-----------------------------------------------------------
Review request for blockerbugs.
Repository: blockerbugs
Description
-------
commit abf5fe2abbcfbce45d103864f5ba40fc89f233fa
Author: Martin Krizek <mkrizek(a)redhat.com>
Date: Tue Jul 16 13:57:28 2013 +0200
Fix sequences in alembic
Sequences need to be created separately. The patch also fixes a few
typos.
https://bitbucket.org/zzzeek/alembic/issue/73/more-pg-nextval-it-needs-the-…
Diffs
-----
alembic/versions/487cb8ccce92_dropping_flask_login.py e64dacb2e3b1a3d14bf38e1116df183ded9793d9
alembic/versions/1d12b74d12bd_add_userinfo_table.py 86dc390ed5e49b0a3ca058e163bc02b070d3d294
Diff: http://reviewboard-tflink.rhcloud.com/r/37/diff/
Testing
-------
Thanks,
Martin Krizek
tflink created this task.
tflink added a subscriber: tflink.
tflink added a project: blockerbugs
TASK DESCRIPTION
I got a report of a failed proposal today where the form said there were errors but everything looks fine and no details were provided.
There is currently no logging of form errors in the app, and that would have been useful in this case. If there's one report, I suspect that there have been other form validation failures which have gone unreported. Attached to this bug is screenshot of what the user reported
{F10}
TASK DETAIL
https://phab.qadevel.cloud.fedoraproject.org/T24
To: tflink
Cc: qa-devel, tflink
mkrizek created this task.
mkrizek claimed this task.
mkrizek added a subscriber: mkrizek.
mkrizek added a project: blockerbugs
TASK DESCRIPTION
Currently, the app knows of no way how to deal with updates that were deleted from bodhi. This results in displaying deleted update as a potential fix for a bug. Also, the app display an obsolete update as a potential fix which it shouldn't.
The update sync code should go through the updates stored in the app's db and somehow mark those that were no longer present in bodhi or that have status 'obsolete' as 'do not display'.
TASK DETAIL
https://phab.qadevel.cloud.fedoraproject.org/T21
To: mkrizek
Cc: qa-devel, mkrizek
jdulaney created this task.
jdulaney claimed this task.
jdulaney added a subscriber: qa-devel.
jdulaney added a project: depcheck mk 2
TASK DESCRIPTION
Currently, depcheck mk 2 uses essentially hard coded links to repodata; better solution is to put these into a config file.
Use yum.repos style so that yum configs can be copied in.
TASK DETAIL
https://phab.qadevel.cloud.fedoraproject.org/T20
To: jdulaney
Cc: qa-devel
#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
#438: Multiple builds fixing a bug show confusing status label
--------------------------------------+---------------------
Reporter: kparal | Owner: tflink
Type: defect | Status: new
Priority: minor | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
See the screenshot. There are two updates that claim to fix a single bug
(that is correct, both of them are needed). One is stable, one is in
testing. The BBA shows [stable] label. That is confusing, that seems to
indicate that everything needed is in stable. (One might happen to visit
that bug and close it, without inspecting it closer).
I think a better choice here is to show the "worst" status in the label.
Therefore:
{{{
update X: stable
update Y: testing
-> label: [testing]
update X: stable
update Y: stable
-> label: [stable]
update X: pending testing
update Y: testing
-> label: [pending testing]
update X: pending stable
update Y: testing
-> label: [testing]
update X: stable
update Y: pending stable
-> label: [pending stable]
}}}
So, if you have an ordered array ['pending testing', 'testing', 'pending
stable', 'stable'], you pick the lowest index available in update XYZ
statuses and show that as the label.
What do you think?
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/438>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#416: irc list sort order doesn't match html buglist
--------------------------------------+------------------------
Reporter: tflink | Owner: tflink
Type: defect | Status: new
Priority: major | Milestone: Fedora 20
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+------------------------
= bug description =
The sort order of the bugs displayed on the html buglist
(milestone/XX/YY/buglist) doesn't match the sort order used when
generating the irc list for meetbot. This causes some confusion and
annoyance when the order of bugs discussed in the meeting is not what
appears in the list that participants are looking at
= fix recommendation =
Make the sort order consistent as component,bzid for both lists
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/416>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#445: upgradepath is failing rawhide builds due to no rawhide-pending
---------------------+------------------------
Reporter: tflink | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests | Keywords:
Blocked By: | Blocking:
---------------------+------------------------
== Description ==
There are several examples where upgradepath is failing builds if rawhide
isn't a newer version (not including release) compared to branched or the
active releases. This is leaving failure messages in bodhi and is leaving
false negatives in bodhi and needs to be fixed.
== Examples of Failure ==
*
http://autoqa.fedoraproject.org/results/681687-autotest/virt04.qa/upgradepa…
/resource-agents-3.9..html#2
*
http://autoqa.fedoraproject.org/results/681759-autotest/virt10.qa/upgradepa…
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/445>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#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
After a conversation with infra, we decided to lock down access to
beaker.fedoraproject.org by IP address until we have a more secure
solution for logins [1].
I've changed the server configuration so that access to beaker is only
allowed from certain IPs. I think that most current users should be
included in this list but if you're seeing 403s and think you should
have access to beaker.fedoraproject.org, please let me know.
Sorry for the inconvenience, we hope to have an alternate access method
soon.
Tim
[1]https://lists.fedorahosted.org/pipermail/beaker-devel/2013-November/00088…
#439: IRC bug order does not match web bug order
--------------------------------------+---------------------
Reporter: kparal | Owner: tflink
Type: defect | Status: new
Priority: minor | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
Look at those two screenshots. Captured at the same time, yet the third
and the fourth bug position is swapped between web ui and IRC script.
Ideally the ordering should be the same. Thanks.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/439>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
tflink created this task.
tflink claimed this task.
tflink added a subscriber: tflink.
tflink added a project: blockerbugs
TASK DESCRIPTION
When logging in, some users are redirected to FAS-OpenID, complete the auth process only to be met with
fails with "Strange state: failure"
TASK DETAIL
https://phab.qadevel.cloud.fedoraproject.org/T23
To: tflink
Cc: qa-devel, tflink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Server Working Group is a team focused on the development of a
server-OS built from the Fedora Project. Recently, the chair held by
Jóhann B. Guðmundsson was vacated. At today's Working Group
meeting[1], we agreed that we would like to approach Fedora QA first
for someone to fill this chair. If you feel that you are able and
willing to represent the interests of Fedora QA in the Server Working
Group, please respond and we will consider you.
Thank you very much in advance.
[1]
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-26/fedora-meeting…
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlKU5CUACgkQeiVVYja6o6OYsQCfbevd04RHvco2HBbY4ZsX81d0
zE8AnjAnAF4QjhkqyucHt7gFZ2Iq3wGZ
=LKJv
-----END PGP SIGNATURE-----
#422: dev instance sync is erroring out with bugzillacookie issues
--------------------------------------+------------------------
Reporter: tflink | Owner: tflink
Type: defect | Status: new
Priority: major | Milestone: Fedora 20
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+------------------------
= bug description =
when the cron scheduled sync runs, it errors out when it can't read the
bugzillacookie file. I thought that we got rid of all the bugzillacookie
references with the fix to #414, so I'm not sure what's going on here.
Filing an issue so it doesn't get lost - this needs to be fixed before we
can release a new version.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/422>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
mkrizek created this task.
mkrizek claimed this task.
mkrizek added a subscriber: mkrizek.
mkrizek added a project: blockerbugs
TASK DESCRIPTION
The task here is to add support for automatic documentation deployment. There is an existing tool for deploying docs generated by sphinx [1] that might be worth looking into. Support for jenkins [2] seems to be missing as of now but is listed as something that will be done in the future. Other thing that needs figuring out is a location of the docs.
[1] https://github.com/teracy-official/sphinx-deployment
[2] http://jenkins.cloud.fedoraproject.org/job/blockerbugs/
TASK DETAIL
https://phab.qadevel.cloud.fedoraproject.org/T22
To: mkrizek
Cc: qa-devel, mkrizek
tflink created this task.
tflink assigned this task to mkrizek.
tflink added a subscriber: tflink.
tflink added a project: blockerbugs
TASK DESCRIPTION
Earlier today, we got a report of the production app throwing 503 errors but the errors went away shortly after. At first glance, it appears that the user in question was logged in at the time and at approximately the same time, the following error showed up on blockerbugs02:
Nov 20 15:30:58 blockerbugs02 app 2013-11-20 15:30:58 ERROR Exception on /admin/ [GET]#012Traceback (most recent call last):#012 File "/usr/lib/python2.6/site-packages/flask/app.py", line 1687, in wsgi_app#012 response = self.full_dispatch_request()#012 File "/usr/lib/python2.6/site-packages/flask/app.py", line 1360, in full_dispatch_request#012 rv = self.handle_user_exception(e)#012 File "/usr/lib/python2.6/site-packages/flask/app.py", line 1358, in full_dispatch_request#012 rv = self.dispatch_request()#012 File "/usr/lib/python2.6/site-packages/flask/app.py", line 1344, in dispatch_request#012 return self.view_functions[rule.endpoint](**req.view_args)#012 File "/usr/lib/python2.6/site-packages/flask_admin/base.py", line 49, in inner#012 abort = self._handle_view(f.__name__, **kwargs)#012 File "/usr/lib/python2.6/site-packages/blockerbugs/controllers/admin/__init__.py", line 43, in _handle_view#012 return check_admin_rights()#012 File
"/usr/lib/python2.6/site-packages/blockerbugs/controllers/users.py", line 52, in check_admin_rights#012 return fas.login()#012 File "/usr/lib/python2.6/site-packages/flask_fas_openid.py", line 129, in login#012 if 'next' in args.values:#012NameError: global name 'args' is not defined
I suspect that something may be mishandled with login when the load balancer sends traffic to the node on which the user did not login initially, but this is just a suspicion - the issue still needs triage.
TASK DETAIL
https://phab.qadevel.cloud.fedoraproject.org/T19
To: mkrizek, tflink
Cc: qa-devel, tflink