always use --nogpgcheck when installing packages
ClosedPublic

Authored by adamwill on Aug 9 2016, 5:43 PM.

Details

Summary

Except when running on the pre-upgrade release in the upgrade
tests (where GPG check should always be OK).

Currently we always need to use --nogpgcheck on Rawhide, and we
must also use it on Branched prior to the Bodhi activation
point. At present we don't really have any simple way to know
when the Bodhi activation point has kicked in. We could assume
that it's safe to do GPG checking for 'candidate' (not nightly)
composes, but even that isn't 100% safe and isn't really the
*right* thing to do. So I think for now it's best to just always
use --nogpgcheck , until we come up with a decent way to check
for Bodhi enablement, or releng figures things out so we can
rely on packages being signed in Rawhide and in Branched before
Bodhi enablement.

Test Plan

Check the tests all still run, make sure I didn't
miss any dnf calls.

Diff Detail

Repository
rOPENQATESTS os-autoinst-distri-fedora
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
adamwill retitled this revision from to always use --nogpgcheck when installing packages.Aug 9 2016, 5:43 PM
adamwill updated this object.
adamwill edited the test plan for this revision. (Show Details)
adamwill added reviewers: garretraziel, jskladan.
garretraziel accepted this revision.Aug 10 2016, 9:29 AM

Yeah, it looks like all necessary dnf runs were covered.

This revision is now accepted and ready to land.Aug 10 2016, 9:29 AM
This revision was automatically updated to reflect the committed changes.