[Fedora QA] #436: SSH access to systems in Beaker lab
by fedora-badges
#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
7 years, 7 months
[Fedora QA] #443: Better format for test compose (TC) and release candidate (RC) requests
by fedora-badges
#443: Better format for test compose (TC) and release candidate (RC) requests
----------------------------------------+------------------------
Reporter: jreznik | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 21
Component: Blocker/NTH review process | Version:
Keywords: | Blocked By:
Blocking: |
----------------------------------------+------------------------
= problem =
With Dennis (in CC), we discussed how to make release process, with
Fedora.next in mind, more transparent and bullet proof. One issue is that
releng request can become pretty messy, with full text included and
sometimes it leads to errors (omission of packages in compose etc).
= enhancement recommendation =
One possibility is to visibly separate full text description (with bug
numbers, reasons - it's good to have history) and the list of exact nvrs
(maybe in code block?), try to avoid "qt bundle" etc. so it's easier to
pick up the right list (for blockers, FEs + exceptional tools requests).
Another thing is better coordination between requester/releng - to mark
when/which list was picked up etc, in similar way how Go/No-Go decision is
stated in the ticket.
Now I'll let more space to Dennis, maybe example of how the request should
look like to make it easy to parse would help.
Long term (and preferred) solution would be to have automation in place,
Blocker app talking to releng interface, compose database, web dashboard
etc...
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/443>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
8 years, 10 months
[Fedora QA] #437: Need to import daily Fedora snapshots into Beaker
by fedora-badges
#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
8 years, 10 months
[Fedora QA] #433: blocker proposal form forgets everything after login timeout
by fedora-badges
#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
8 years, 10 months
relval progress report
by Adam Williamson
hey, folks - just in case no one spotted it on test@, I have been
moonlighting as a python developer lately...
https://www.happyassassin.net/cgit/relval/
is a little thing I'm writing with the initial goal of making the
process of kicking off a release validation event easy. In the true
tradition of software projects, it already has a hopelessly confused
naming history: it's now officially the module 'wikitcms' with the
command line tool 'relval', but I didn't get around to renaming the
repository yet...
right now it'll create the validation result pages for an event, and
handle categories: it deals with the limitation in the magic template
system that results in pages being in the wrong category, and makes sure
the whole hierarchy of categories up to Test_Results is correct (per the
SOP) each time you create an event.
I'm trying to write it in such a way as to be reasonably extensible and
re-usable, with an eye to making it do more later. I just had a quick
look, and I think it may be possible to either fold testcase_stats into
it, or rewrite testcase_stats to use it as a backend for at least some
stuff and simplify it. testcase_stats is written to do MW API calls
itself, which it doesn't really need to do, it could use mwclient as
relval/wikitcms does, and it can probably use some of wikitcms'
knowledge of what pages should exist for what events and so on. I do
mean to add a property of ComposeEvent() which would be the result pages
that currently actually exist for that event.
i'd be very grateful for your comments / mocking laughter ;) thanks
folks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 1 month
2014-09-30 21:00 UTC - AutoQA and Taskotron Downtime
by Tim Flink
With the scheduled infra downtime today, all Taskotron and AutoQA
systems will be down for reboots and updates starting at 21:00 UTC.
I'll send out another email when the downtime is complete.
Tim
9 years, 2 months
2014-09-22 @14:00 UTC - QA Devel Meeting
by Tim Flink
Apologies for the delay in sending out a specific agenda. If you have
any items to add, feel free to reply here or bring them up in meeting.
* Moving Taskotron to Production
- remaining tasks, status
* Status Update
- execdb
- disposable clients
- remote logging
* Iteration 6
- task claiming etc.
9 years, 2 months
taskotron.stg is not currently working
by Tim Flink
After upgrading Taskotron staging earlier today, the trigger stopped
working. Martin and I have been trying to fix it but we're out of ideas
as to why trigger isn't working and the apps folks don't see anything
wrong with the config, either.
We're aware of the problem and I'm planning to pester Ralph about it
tomorrow if we can't get it figured out today.
Tim
9 years, 2 months