[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, 5 months
openQA: Rawhide needle issues
by Adam Williamson
Hi folks! We finally got a Rawhide compose with a non-busted anaconda
for the first time in a while today. Several of the tests are failing
on needle match issues. It seems like rendering of some text elements
has changed in Rawhide anaconda. I'm not sure whether the anaconda
folks actually want it to look that way now, or if these would be
considered rendering errors and they're caused by a GTK+ change or
something. I will talk to the anaconda folks about it in the morning
(my time) before we go through and create new needles.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 6 months
Proposal to CANCEL: 2016-03-28 Fedora QA Devel Meeting
by Tim Flink
Monday is a holiday in the Czech Republic and that means a lot of folks
won't be present - to the point where I don't think it'll be productive
to hold a meeting.
If there is a topic that you would like to see discussed, reply to this
thread with that topic and we can hold the meeting as it would have
been scheduled.
Tim
7 years, 6 months
openQA update: chained test failures
by Adam Williamson
Hi folks!
So those of you who watch the openQA results might have noticed that
for the last month or so, there have been lots of problems with the
'chained' tests - the _base_ tests that run for various of the media
after default_install has been run, and use a hard disk snapshot
uploaded by default_install.
I think I've made some progress on this. I've made one change, and
proposed another. The first change: I made it possible to configure
openQA's total asset size limit in the Ansible plays for deploying
openQA, and set the limit for our deployments to 300GB (the default is
100GB):
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit?id=cb7bf...
(plus a couple of follow-up commits). That's the value that openQA uses
for cleaning up old assets: when there's more than that amount of
assets, it wipes some. What I suspect was happening there is that since
we already have more than 100GB of assets all the time (...depending on
exactly how you count, there's some subtlety there) gru was sometimes
wiping uploaded disk images as part of the 'remove old assets' task
before they could be used. This, I think, accounts for the cases where
the chained tests did not run at all, and reported 'setup failure'.
The second change: https://phab.qadevel.cloud.fedoraproject.org/D787 .
What that does is make it so that tests which upload a disk image try
to shut down the VM cleanly before doing so. Without that change, we
were actually uploading the disk image file while the virtual machine
was still running, I think. I believe that was the cause of the cases
where the Server DVD post-install tests ran, but all failed due to the
system failing to reach a login prompt at all.
I'm hoping with D787 reviewed and applied, almost all openQA tests
should be working again. We're left only with the i386 kernel problem
and whatever's going wrong with server_kickstart_hdd (I don't *think*
that's a corrupt image problem like server_updates_img_local was, I
think it may be a genuine bug).
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 6 months
Proposal to CANCEL: 2016-03-21 Fedora QA Devel Meeting
by Tim Flink
I don't have any hugely important topics for the QA Devel meeting this
week so instead of taking up 30-60 minutes of everyone's time this
week, I propose that the meeting be canceled.
If there is a topic that you would like to see discussed, reply to this
thread with that topic and we can hold the meeting as it would have
been scheduled.
Otherwise, I'll sync up with folks about tasks during the week.
Tim
7 years, 6 months
Quick update on openQA / check-compose / validation event creation
status
by Adam Williamson
Hey folks! Just so I'm not the only one who knows this, here's a quick
update on how all the compose process magic I'm dealing with is working
now.
We now have three fedmsg-hub consumer implementations:
1. OpenQAConsumer (lives in openqa_fedora_tools)
2. CheckComposeConsumer (lives in fedora-qa/check-compose)
3. RelvalConsumer (lives in fedora-qa/relvalconsumer)
The first two are running on the openQA server hosts, installing and
enabling them is part of the ansible plays:
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/open...
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/chec...
The third is running on my web server. This is not for any good reason,
it's just because that's where we used to do the same job. It could
really run anywhere, we just need to make sure exactly one of its
RelvalProductionConsumer instances is running somewhere all the time.
All three listen out for the
org.fedoraproject.prod.pungi.compose.status.change fedmsgs for Pungi 4
composes and fire when the status is FINISHED or FINISHED_INCOMPLETE.
The first two also listen for
the org.fedoraproject.prod.compose.23.cloudimg-staging.done messages
for two-week Atomic nightly composes, RelvalConsumer does not, because
we do not create validation events for those.
OpenQAConsumer creates openQA jobs for new composes. Right now we do
*not* have anything which reports results to the wiki, because we don't
have openQA emitting fedmsgs and we can't have a consumer block for two
hours waiting for tests to finish. I'm hoping to get openQA emitting
fedmsgs soon; if this turns out to be harder than anticipated, we can
use the same hack CheckComposeConsumer uses (see below).
CheckComposeConsumer produces the 'compose check' emails. In order to
do this, the openQA jobs have to be finished, but we don't have a
fedmsg for that. So as a temporary hack, the consumer simply forks off
a run of the `check-compose` script, which will wait for the openQA
jobs to complete, then send the email. One limitation of this is that
if the fedmsg-hub service gets killed or restarted while a check-
compose process is sitting there waiting for openQA jobs to finish, the
check-compose process gets killed, because it's part of the hub
service's cgroup. I haven't found a way to avoid this yet (the attempt
in the code only works for process groups, and systemd acts on
cgroups). So we can lose mails if we get fedmsg-hub restarts at
unfortunate times.
RelvalConsumer creates release validation events (i.e. it makes all the
wiki pages and sends out an announcement mail). It does exactly the
same job that used to be done by a cron job on the same box which ran
`relval nightly --if-needed` every day, at a time we hoped the compose
was complete. It uses all the same logic, so it should create events on
much the same frequency as before. Note it actually *replaces* relval
for this task, it does not use it; it actually uses wikitcms directly.
Right now, it only handles nightlies. This is because we still haven't
decided what milestone composes will look like, so I couldn't write the
code to handle them. But once we *do* decide that, I intend to enhance
the consumer to handle them, and all compose event creation will
entirely automated (we won't have to run relval by hand to create
milestone events, as we have had up till now).
Longer term I would like to make it so all these things are taskotron
tasks, obviously. We just need to work through the process of adding
the trigger and resolving the question of how we run the tasks in an
environment with the necessary credentials available.
-- Adam WilliamsonFedora QA Community MonkeyIRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . nethttp://www.happyassassin.net
7 years, 6 months
Workboards and Sprints
by Tim Flink
After talking about the workboards in phabricator during the meeting
earlier today, I mentioned trying to figure out a way to have
workboards for more than just a single project.
I've been futzing around with qadevel-stg today and have a proposal to
make.
* Keep the existing projects
* Remove workboards from at least the Taskotron related projects
(libtaskotron, resultsdb, taskotron-trigger etc.)
* Create a new project named "QA Devel" which has the same workboard
columns as the libtaskotron workboard currently does.
The "process" for getting tasks proposed and worked on would then be:
1. add the "QA Devel" tag to the task, putting it on the "backlog" for
that project
2. If the task has enough detail to move forward, it can move to
"groomed"
3. Immediate priorities are in the "On Deck" column, in priority order
from top to bottom
4. In progress and "ready for completion" are pretty self explanatory
I'd also like to start a 2 week cadence again. It may go away again as
we get closer to F24 final but I think it will help organize things a
bit better.
Thoughts?
Tim
7 years, 6 months
2016-02-29 @ 15:00 UTC - Fedora QA Devel Meeting
by Tim Flink
# Fedora QA Devel Meeting
# Date: 2016-02-29
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
Don't miss the special Leap Year edition of the Fedora qadevel meeting
- February 29th doesn't happen every year!
On a more serious note, there are a few items up for discussion but I'm
hoping they won't take too long.
Please put announcements and information under the "Announcements and
Information" section of the wiki page for this meeting:
https://phab.qadevel.cloud.fedoraproject.org/w/meetings/20160229-fedoraqa...
Tim
Proposed Agenda
===============
Announcements and Information
-----------------------------
- Please list announcements or significant information items below so
the meeting goes faster
Workboards and Sprints
----------------------
Discuss and possibly start on the discussion started on list last week
Tasking
-------
- Does anyone need tasks to do?
Potential Other Topics
----------------------
- dist-git style tasks
Open Floor
----------
- TBD
7 years, 7 months
