Bug 1400682

Summary:	fedora repository gpg key isn't imported
Product:	[Fedora] Fedora	Reporter:	Georg Sauthoff <fedora>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	anaconda-maint-list, dustymabe, g.kaviyarasu, jonathan, mkolman, rvykydal, vanmeeuwen+fedora, vponcova
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 10:04:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Georg Sauthoff 2016-12-01 19:47:49 UTC

Description of problem:
Ananconda doesn't import the GPG key /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64 as part of finalizing the installed system.

It would make to do so because:

1. it is safe (because it is included in the ISO which the user already has cryptographically verified before booting it)
2. it is tedious to have to manually acknowledge its import on the first `dnf install` call
3. it is tedious to add and maintain a `rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora...` in each provisioning playbook

Version-Release number of selected component (if applicable):


How reproducible:
always


Steps to Reproduce:
1. boot the - say - fedora workstation 25 ISO and do a standard install
2. reboot into the new system
3. dnf install vim # which is not installed yet

Actual results:
dnf asks if you want to import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64

Expected results:
no key warning message and no prompting for installing the key

Additional info:
With the workstation network ISO the situation is even more absurd:

1. you download the iso and you decide that you trust it after cryptographically verifying it
2. during the install many packages are installed over the network
3. since bug #998 is resolved those packages should be verified, i.e. probably via the gpg key
4. after the first boot of the new system the system is up-to-date, but the first `dnf install` call asks me if I **still** trust the gpg key and if I want to import it.

Comment 1 Dusty Mabe 2017-01-11 16:42:39 UTC

can we please get this fixed for F26?

Comment 2 Fedora End Of Life 2017-11-16 18:34:56 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:04:26 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.