DevHeads.net

Postings by Adam Williamson

openQA brief outage

Hey folks! Heads up: there is a brief openQA outage at present while I
upgrade the production instance to Fedora 26. Staging was already
upgraded last week, so there shouldn't be any big problems. Thanks!

Blocker bug process proposal: waiving late-discovered blockers to next release

Hi, folks!

So, during the blocker review process in the last few cycles, we have
several times come up against the unfortunate situation that a bug that
in the usual course of events would block a release is discovered
extremely late - say the day before the go/no-go meeting - and at least
some folks have argued that it's sometimes appropriate to not block the
release in this case.

This position has gained quite a bit of acceptance, and we agreed at
the F26 Final go/no-go meeting to draft up some formal policy for this
so we can make such decisions consistently and not in an ad hoc way
that

2017-07-17 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-07-17
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We didn't get through everything last week, so let's have a follow-up
meeting.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 27 planning
3. Storage test matrix update status
4. Open floor

2017-07-10 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-07-10
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

Fedora 26 is signed off, so let's check in on its status and any
remaining tasks, then take a first look at what's coming up in the
Fedora 27 cycle.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 26 status / retrospective
3. Fedora 27 planning
4. Test Day status
5. Open floor

Fedora 26 Candidate RC-1.5 Available Now!

** NOTE ** RC-1.5 is a kind of 'conditional' compose. The sole
difference to RC-1.4 (bar anything that went odd in the compose
process) is the qemu update for
<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde">https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde</a> . So
aside from virt guest tests, most other results should be transferable
from RC-1.4. Still, at least smoke testing each image would be great.
We may wind up shipping RC-1.4, shipping RC-1.5, or not shipping
either; it'll be decided at the Go/No-Go meeting in the morning.

According to the schedule [1], Fedora 26 Candidate RC-1.5 is now
available for testing.

Another Fedora 26 test request: VMware

Hi folks! Got another request for Fedora 26 Final testing: can folks
please try booting RC-1.4 in VMware? For me, the Workstation live fails
to boot properly, in various configurations; in comparison the F25
Final Workstation live boots fine. That worried me a bit, so it'd be
good to hear results from other testers...

Fedora 26 status and testing requests: qemu , totem , and validation

Hi folks! Just wanted to send out a roll-up mail with some specific
requests for testing related to the Fedora 26 release.

1. There's a new qemu build which should fix the proposed blocker
#1467599 . It would be great if anyone who runs F26 and uses virt-
manager, Boxes or qemu in any other way could update to it and check
that it works OK:

<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde">https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde</a>

We don't just need testing from folks who were affected by the bug, but
by anyone who uses qemu, to ensure the change doesn't cause any other
problems.

2.

Fedora 26 Candidate RC-1.4 Available Now!

According to the schedule [1], Fedora 26 Candidate RC-1.4 is now
available for testing. Please help us complete all the validation
testing!

Proposal to CANCEL: 2017-07-03 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting tomorrow. It's a
holiday in the U.S. and in Canada, and in any case we have little to
discuss right now as our efforts should mainly be focused on Fedora 26
Final testing. If you're aware of anything that urgently needs
discussing, please do reply to this mail and we can try to go ahead and
run the meeting, though it depends on people being around to run and
attend it.

Fedora 26 Candidate RC-1.3 Available Now!

** NOTE ** : This is the first 'real' release candidate for Fedora 26
Final. All known blocker bugs are addressed. Please do help us test it
as much as possible! This announcement is being sent manually because
the bot that's supposed to do it seems to be on the blink, I'll deal
with that tomorrow.

According to the schedule [1], Fedora 26 Candidate RC-1.3 is now
available for testing. Please help us complete all the validation
testing!

Reminder: Fedora 26 Upgrade Test Day tomorrow

Just a reminder, as the announcement was over a week ago, that tomorrow
is Fedora 26 Upgrade Test Day in #fedora-test-day on Freenode!

<a href="https://fedoraproject.org/wiki/Test_Day:2017-06-30_Upgrade_Test_Day" title="https://fedoraproject.org/wiki/Test_Day:2017-06-30_Upgrade_Test_Day">https://fedoraproject.org/wiki/Test_Day:2017-06-30_Upgrade_Test_Day</a>

Please come out and help test if you can. Thanks!

Proposal to CANCEL: 2017-06-26 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting tomorrow.
There's nothing in particular to discuss at a meeting right now, so far
as I know. If you're aware of anything, please do reply to this mail
and we can go ahead and run the meeting.

We do have the blocker review meeting at 1600 UTC, so see you there!

2017-06-19 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-06-19
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

Beta is signed off now, so let's check in on the libdb mess, where we
stand with Final, and what else is going on.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 26 status / libdb issues
3. Test Day status
4. Open floor

Proposal to CANCEL: 2017-06-12 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. We did a
pretty good job of checking in this week, and I don't think there's
anything pressing that needs a meeting this week. The status of Beta is
a bit of a mess with the remaining libdb issues, but that needs to be
discussed at a different level than the QA team.

If anyone does want to have a meeting and is willing to run it, please
just go ahead and say so (and send out an agenda).

Mike will be sending out a blocker review meeting announcement for
Tuesday, I believe.

2017-06-05 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-06-05
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

Sorry for the late notice, but we haven't met for a while, and it'd
probably be good to check in on the status of Beta and some other
upcoming events and ongoing activities.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 26 status
3. Test Day status
4.

Testing request: libdb and F26 upgrades

Hi folks!

So as you may have read, F26 Beta was held up by a tricky bug which
causes upgrades to hang in some situations:

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1397087" title="https://bugzilla.redhat.com/show_bug.cgi?id=1397087">https://bugzilla.redhat.com/show_bug.cgi?id=1397087</a>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1394862" title="https://bugzilla.redhat.com/show_bug.cgi?id=1394862">https://bugzilla.redhat.com/show_bug.cgi?id=1394862</a>

There are updates in F24, F25 and F26 at present which we hope should
resolve this bug without causing other problems, but the code in
question is quite sensitive so we want to be as sure as possible that
it's good to go.

It would be great if folks can help test.

Proposal to CANCEL: 2017-05-29 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. There are a
few things we could talk about, but none of them is really urgent, we
still have Beta testing to do, Monday's a vacation in the U.S., and I'm
also moving house that day so I won't be around!

If anyone does want to have a meeting and is willing to run it, please
just go ahead and say so (and send out an agenda).

Mike will be sending out a blocker review meeting announcement for
Tuesday, I believe.

RPM database issues in the last day or two

Hi folks!

If you ran into problems like RPM or dnf or related apps reporting
database errors or unexpected crashes in the last few days, it is
almost certainly due to a broken libdb update that was sent to updates-
testing briefly. libdb-5.3.28-18 and libdb-5.3.28-19 are both subject
to the bug. If you got either of those builds while they were in
updates-testing for F24, F25 or F26, please do downgrade back to libdb-
5.3.28-17 .

Proposal to CANCEL: 2017-05-22 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. We should
mostly be focused on Beta validation now, and I don't see any major
other topics that need discussing right now. If you're aware of any,
please do reply to this mail and we can go ahead and run the meeting.

Remember, we do have the blocker review meeting at 1600 UTC!

2017-05-15 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-05-15
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We haven't met for a bit, and we're coming up on the Beta freeze,
so let's have a quick check-in!

Fedora 26 Beta blocker status mail #1

Hi folks! The Fedora 26 Beta freeze is fast approaching (it's 2017-05-
16), so it's time for a blocker status mail.

tl;dr action summary
====================

1. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1448923" title="https://bugzilla.redhat.com/show_bug.cgi?id=1448923">https://bugzilla.redhat.com/show_bug.cgi?id=1448923</a>
ACTION: Preferably, Firefox maintainer (mstransky) to fix build on ARM

2. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1443415" title="https://bugzilla.redhat.com/show_bug.cgi?id=1443415">https://bugzilla.redhat.com/show_bug.cgi?id=1443415</a>
ACTION: dnf team to investigate problem and come up with a fix

3. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1446432" title="https://bugzilla.redhat.com/show_bug.cgi?id=1446432">https://bugzilla.redhat.com/show_bug.cgi?id=1446432</a>
ACTION: QA to build a test image and verify fix

4.

Proposal to CANCEL: 2017-05-08 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting tomorrow,
unless someone else wants to run it. I'm on my way back home from
Linuxfest Northwest and will be getting in pretty late, and I'm not
sure I'm going to make it up to run a meeting. If anyone would like to
volunteer to run the meeting, please just go ahead and send out an
agenda.

Remember, we do have the blocker review meeting at 1600 UTC!

Some dates for your diary: Beta freeze is 2017-05-16, and Beta Go/No-Go
is scheduled for 2017-05-25.

Proposal to CANCEL: 2017-05-01 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't
have anything significant to discuss.

If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.

openQA test results for critpath updates now shown in Bodhi

Hi folks! I thought this was worth sending out an announcement about so
as many packagers and testers as possible are aware of it.

With the rollout of Bodhi 2.6.0 to production today, openQA test
results for critpath updates now appear in the Bodhi webUI! Click the
'Automated Tests' tab on any critical path update (from the last two
months or so) and you should see, as well as the 'dist.*' tests you're
probably familiar with that are run by Taskotron, results for several
'update.*' tests.

2017-04-24 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-04-24
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

I don't have a big agenda this week, but figured we might as well get
together for a quick check-in. We might go less than an hour if there
isn't a lot to talk about.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 26 status
3. Test Day status
4. Action ideas?
5. Open floor

Proposal to CANCEL: 2017-04-17 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. It's a
holiday in many parts of the world, and we don't have anything specific
to discuss, I don't think.

If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.

2017-04-10 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-04-10
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We have some active criteria / validation test proposals to discuss,
so that's a reason to have a meeting. And there appears to be stuff
ongoing in Atomic-land, I thought maybe roshi might know about that
and could update us.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2.

2017-04-03 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2017-04-03
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We haven't met for a couple of weeks, so let's get together and see
what's happening.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 26 status
3. Test Day status
4. Open floor

Proposal to CANCEL: 2017-03-27 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting tomorrow. Once again I
don't have anything significant for the agenda as we're mostly busy
with Alpha validation. We'll likely have stuff to check in on next week.

If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.

Fedora 26 Alpha status update

Hi folks! Just wanted to let everyone know where we're at with the F26
Alpha.

An Alpha RC2 compose request is in, and RC2 should be building at
present. The main change between RC1 and RC2 is a fix for the problems
with gnome-initial-setup: it should now work properly if you don't
create a user during install. There's also an updated selinux-policy
which should hopefully squish all the AVCs we've been seeing during
regular install and boot. It should arrive some time this evening US
time, all being well.

There does still seem to be some kind of kernel issue.