December 2013 - qa-devel - Fedora mailing-lists

[Fedora QA] #436: SSH access to systems in Beaker lab
by fedora-badges 20 Apr '16

20 Apr '16

#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

1 4

[Fedora QA] #437: Need to import daily Fedora snapshots into Beaker
by fedora-badges 29 Jan '15

29 Jan '15

#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

1 1

[Fedora QA] #433: blocker proposal form forgets everything after login timeout
by fedora-badges 20 Jan '15

20 Jan '15

#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

1 2

Review Request 37: Fix sequences in alembic
by Martin Krizek 21 Feb '14

21 Feb '14

----------------------------------------------------------- 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

1 4

Review Request 62: Fix needinfo field length
by Martin Krizek 21 Feb '14

21 Feb '14

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/62/ ----------------------------------------------------------- Review request for blockerbugs. Repository: blockerbugs Description ------- Now that we support multiple needinfo flags, we also need to increase length of the needinfo field. Diffs ----- blockerbugs/models/bug.py 695d0ce3ca800ad8cd8d8324bc01726a84eade1b alembic/versions/1dfd879c7637_fix_needinfo_field_l.py PRE-CREATION Diff: http://reviewboard-tflink.rhcloud.com/r/62/diff/ Testing ------- Testing done on my dev machine. Thanks, Martin Krizek

1 1

Review Request 61: Rename line.png to line-bottom.png
by Martin Krizek 21 Feb '14

21 Feb '14

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/61/ ----------------------------------------------------------- Review request for blockerbugs. Repository: blockerbugs Description ------- It appears that we've been getting ""GET /static/img/line-bottom.png HTTP/1.1" 404" for quite some time now... commit fb18e118d108a8965a2ea8a2087bf1baa88cc193 Author: Martin Krizek <mkrizek(a)redhat.com> Date: Tue Dec 17 10:47:34 2013 +0100 Rename line.png to line-bottom.png to reflect the actual state of css. Diffs ----- blockerbugs/static/img/line.png 6c111c3c3ed2118dfe803e02a6b0c8245010082a blockerbugs/static/img/line-bottom.png PRE-CREATION Diff: http://reviewboard-tflink.rhcloud.com/r/61/diff/ Testing ------- Thanks, Martin Krizek

1 1

Review Request 60: Insufficient logging for bug proposal form issues
by Martin Krizek 21 Feb '14

21 Feb '14

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/60/ ----------------------------------------------------------- Review request for blockerbugs. Repository: blockerbugs Description ------- Errors were logged with level 'debug' which caused them to not being logged at all on prod. commit cb8169121c4c27ef8893eef11b8b0b0ef7f1dea7 Author: Martin Krizek <mkrizek(a)redhat.com> Date: Tue Dec 17 15:11:26 2013 +0100 Set log level to 'error' for errors in the blocker proposal form Fixes: T24 Diffs ----- blockerbugs/templates/propose_bug.html 848a3e2bd7b94780348a107230f057801c7ea868 blockerbugs/controllers/main.py 5455e1aa2bbf6edc551223ee6fccb9c6236f0eb8 Diff: http://reviewboard-tflink.rhcloud.com/r/60/diff/ Testing ------- Thanks, Martin Krizek

1 1

[Maniphest] [Created] T24: Insufficient logging for bug proposal form issues
by tflink (Tim Flink) 15 Jan '14

15 Jan '14

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

1 3

RFC: Taskotron task description format
by Tim Flink 15 Jan '14

15 Jan '14

I've been working on this for a bit but finally have enough together that we can start talking about the task description format for taskotron. The code to actually run tasks (well, task. for now, rpmlint is all that's supported) is up at: https://bitbucket.org/fedoraqa/libtaskotron-demo The runner code isn't very good yet but I didn't want to wait until it was done before starting to discuss the task description format. Continuing the use of rpmlint as an example, I have a task repository set up on bitbucket: https://bitbucket.org/fedoraqa/task-rpmlint At the moment, that task yaml file for rpmlint [1] looks like: dependencies: - rpmlint - libtaskbot input: args: envr,arch preparation: koji: download $envr execution: python: run_rpmlint.py $workdir post: shell: clean $workdir report: resultdb: something [1]https://bitbucket.org/fedoraqa/task-rpmlint/src/be90c723a11f3cec3a7ee72e3… In a nutshell, the idea is to keep repetitive code out of the tasks without requiring everything to be written in the same language or porting the library to any language people want to use (perl, c, bash etc.). The execution of the task is described in the yml file and eventually delegates actual execution to the python file described in that yml file. Output, for now, is in TAP format. The runner just spits it out as text for the moment but eventually, that TAP output will be used for reporting the results. Items prepended with '$' represent variables - either things determined at runtime (the working directory) or things that are arguments to the specific task run (the envr of packages to check). Examples of what future features could look like: execution: beaker: job=somejob.xml distro=$latestfedora preparation: bodhi: download $updates preparation: openstack: image=imagename config=someconfigtype size=m1.small execution: infinity: config=test/sometest.cfg Any thoughts on whether this direction is a good direction to take or suggestions on how the format could be improved? Eventually, I want to send this out to devel@ for input but figured that the smaller group of folks here would be a good start. Thanks, Tim

4 6

[Maniphest] [Created] T21: Do not display obsolete and deleted updates
by tflink (Tim Flink) 14 Jan '14

14 Jan '14

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

1 2

[Maniphest] [Created] T20: Use config files to point to repodata locations in depcheck mk 2
by tflink (Tim Flink) 13 Jan '14

13 Jan '14

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

1 2

[Fedora QA] #381: Bug and Update syncs shouldn't be halted by an isolated problem with one update or bug
by fedora-badges 13 Jan '14

13 Jan '14

#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

1 1

[Fedora QA] #384: Improve documentation
by fedora-badges 13 Jan '14

13 Jan '14

#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

1 1

[Fedora QA] #440: show also closed bugs
by fedora-badges 13 Jan '14

13 Jan '14

#440: show also closed bugs --------------------------------------+--------------------- Reporter: sharkcz | Owner: tflink Type: enhancement | Status: new Priority: major | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- I would like to be able to see also closed blocker bugs, not only the pending ones. The current setup can be the default and have a check box for showing the closed ones. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/440> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

AutoQA 0.8.5 Released
by Tim Flink 18 Dec '13

18 Dec '13

The AutoQA developers are proud to announce the release of AutoQA 0.8.5 today. This is a maintenance release with the following changes: - Improved clarity in upgradepath output (#445) - Updated repository configuration for F20 release The new version has been deployed to our staging environment and will be moved to production later this week if no issues manifest. Thanks, Tim

1 0

[Maniphest] [Created] T25: Allow users to see which bugs have changed blocker status in the last X hours/days
by tflink (Tim Flink) 18 Dec '13

18 Dec '13

tflink created this task. tflink added a subscriber: tflink. tflink added a project: blockerbugs TASK DESCRIPTION There was a feature request to be able to tell which bugs in the lists have changed blocker state (as opposed to the bugzilla state change that we currently highlight) in the last day or so. Some investigation would be needed to figure out where it could fit into the current UI and how much work would be required. TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T25 To: tflink Cc: qa-devel, tflink

1 1

Review Request 59: Show number of blockers/FEs in titles in the blocker list
by Martin Krizek 17 Dec '13

17 Dec '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/59/ ----------------------------------------------------------- Review request for blockerbugs. Repository: blockerbugs Description ------- kparal had an idea of displaying number of blockers/FEs in titles in the blocker list, this is what I came up with. commit d96ed8d6b5c196f9750cf5e062a6fc958e35821c Author: Martin Krizek <mkrizek(a)redhat.com> Date: Mon Dec 16 14:31:22 2013 +0100 Show number of blockers/FEs in titles in the blocker list. With this patch, titles now look like e.g. these: 1 Proposed Blocker No Accepted Blockers 2 Accepted Freeze Exceptions Diffs ----- blockerbugs/templates/blocker_list.html ea79d9ba852a5147a362cd904f853c77bd03c54a Diff: http://reviewboard-tflink.rhcloud.com/r/59/diff/ Testing ------- Testing done on my dev machine. Thanks, Martin Krizek

1 2

Review Request 57: Multiple builds fixing a bug show confusing status label
by Martin Krizek 16 Dec '13

16 Dec '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/57/ ----------------------------------------------------------- Review request for blockerbugs. Bugs: 438 https://fedorahosted.org/fedora-qa/ticket/438 Repository: blockerbugs Description ------- commit 911781af9cc06e27c0a8580f07f7673c90e7329d Author: Martin Krizek <mkrizek(a)redhat.com> Date: Tue Dec 10 16:28:52 2013 +0100 Sort updates by (status.desc(), pending.desc()) This way an update label is correctly set when multiple updates fix a bug. The label is chosen by the following order (the lowest one): pending testing < testing < pending stable < stable Fixes: #438 Note: the rest of the issues with displaying label is handled outside this ticket in https://phab.qadevel.cloud.fedoraproject.org/T26 Diffs ----- blockerbugs/models/update.py 89c083da5c91558d4dead118c67e4a1138b8cae1 blockerbugs/controllers/main.py 1795ed1d717bb85e0f3d9e7e7008d68c2aae36d8 blockerbugs/__init__.py dcf6c5aadb24e6d86e95d5bb3d608b81721de47f Diff: http://reviewboard-tflink.rhcloud.com/r/57/diff/ Testing ------- Sorting seems to be working as expected. Thanks, Martin Krizek

1 7

[Fedora QA] #438: Multiple builds fixing a bug show confusing status label
by fedora-badges 16 Dec '13

16 Dec '13

#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

1 2

[Maniphest] [Created] T27: Irrelevant "phantom" updates are not purged from active update list
by tflink (Tim Flink) 11 Dec '13

11 Dec '13

tflink created this task. tflink added a subscriber: tflink. tflink added a project: blockerbugs TASK DESCRIPTION Currently, there are two anaconda updates displayed in the blocker tracking app. One is current, one is a phantom update that no longer exists in bodhi. The phantom update appears to have come from the fact that updates don't get UIDs before being pushed to updates-testing. This particular update was modified after the blocker tracking app picked it up but before the update was pushed to updates-testing. This means that the title changed before we could get the UID and we detected two different updates - one valid and one invalid. Regardless of the method by which the "phantom" updates are showing up, the update sync algorithm should be removing any phantom or invalid updates from the list. TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T27 To: tflink Cc: qa-devel, tflink

1 1

[Maniphest] [Created] T26: Display all users that are listed in needinfo flag
by tflink (Tim Flink) 11 Dec '13

11 Dec '13

mkrizek created this task. mkrizek claimed this task. mkrizek added a subscriber: mkrizek. mkrizek added a project: blockerbugs TASK DESCRIPTION Currently only the first user that info is needed from in bugzilla is displayed. The task here is to display all of them. TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T26 To: mkrizek Cc: qa-devel, mkrizek

1 1

Review Request 58: Display all users that are listed in needinfo flag
by Martin Krizek 11 Dec '13

11 Dec '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/58/ ----------------------------------------------------------- Review request for blockerbugs. Repository: blockerbugs Description ------- commit 0618ae3bc89431f9d00a3cc103b19fc0376697ed Author: Martin Krizek <mkrizek(a)redhat.com> Date: Wed Nov 20 14:51:17 2013 +0100 Display all users that are listed in needinfo flag Also this adds tests for needinfo flag and updateid. Fixes: T26 Diffs ----- testing/testfunc_update_sync.py 14e7efca3b01d29f6d791d5cddce74609161ad66 testing/testfunc_bugsync.py f1a106379484330ef16eaf5bd18a91c65919ce98 testing/testfunc_bugmodel.py 640a63303c696359d324782ff36c5c16d0f4c357 testing/test_updatesync_extract_information.py 771faabf8a4076ed3ee5f9eb3865eb1deda7f7ae testing/test_controllers.py 7a6a3725c6570754cc55d916d1156ddc33478f10 testing/test_bugsync_extract_information.py e7c8ed08e5a71f5b81c164ebed24e7188e7a69a7 blockerbugs/util/bug_sync.py ae077231aea97f4c5918a4f37b21a1655b049984 Diff: http://reviewboard-tflink.rhcloud.com/r/58/diff/ Testing ------- Tests included in the patch. Thanks, Martin Krizek

1 2

[AutoQA] #446: [rpmguard] preun/postun scripts change
by fedora-badges 11 Dec '13

11 Dec '13

#446: [rpmguard] preun/postun scripts change --------------------------+---------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Rpmguard Component: tests | Keywords: Blocked By: | Blocking: --------------------------+---------------------- It would be nice to add notifications about preun/postun scripts change. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/446> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 0

[Fedora QA] #416: irc list sort order doesn't match html buglist
by fedora-badges 09 Dec '13

09 Dec '13

#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

1 6

[AutoQA] #445: upgradepath is failing rawhide builds due to no rawhide-pending
by fedora-badges 09 Dec '13

09 Dec '13

#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

1 9

Disambiguation of beaker.fedoraproject.org
by Tim Flink 05 Dec '13

05 Dec '13

There still seems to be a bit of confusion as to the current state of the beaker deployment that we've been working on for Fedora. To improve clarity on the exact state of the current install, I've made some changes to what was formerly beaker.fedoraproject.org: - The beaker server is now available at beaker-dev.fedoraproject.org - beaker.fedoraproject.org points to a static html page explaining what beaker-dev.fedoraproject.org is, how to reach it and that it is currently access restricted while the security issues are dealt with. I've also enabled SSL with self-signed certs and disallowed non-https traffic to the beaker server but the previous IP access restrictions still apply. Tim

2 1

[Fedora QA] #431: Enable HTTPS for beaker.fp.o
by fedora-badges 03 Dec '13

03 Dec '13

#431: Enable HTTPS for beaker.fp.o --------------------------------------+--------------------- Reporter: atodorov | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- Please enable HTTPS for beaker.fp.o. Can be self-signed or a wildcard *.fp.o certificate if there is one. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/431> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #387: Updates pending stable show as stable
by fedora-badges 02 Dec '13

02 Dec '13

#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

1 4

Locking Down Access to Beaker
by Tim Flink 01 Dec '13

01 Dec '13

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…

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

qa-devel December 2013