Bug 859434

Summary:	Set gpgcheck to 1 if a new gpgkey is updated and set
Product:	Red Hat Enterprise Linux 7	Reporter:	David Davis <daviddavis>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED DUPLICATE	QA Contact:	Entitlement Bugs <entitlement-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	bkearney, daviddavis, jsherril, omaciel
Target Milestone:	beta
Target Release:	7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-22 20:44:56 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:
Embargoed:
Bug Depends On:
Bug Blocks:	863175

Description David Davis 2012-09-21 14:29:46 UTC

Description of problem:

In katello, if I add a gpgkey to an existing subscription, then it gpgcheck remains 0. It would be nice if instead the gpgcheck got switched to 1.


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

subscription-manager-0.99.19-1.el6.x86_64


How reproducible:

On a scale from 1-10, like 8 or 9.


Steps to Reproduce:

I'm not sure how to do this outside of katello :(

1. Create a org, environemnt, and product with repos in katello. Do not add a gpg key.
2. Create a client, add it to the env, and subscribe it to the product.
3. Go onto the client and install the cp rpm. Then run "subscription-manager refresh && yum repolist"
4. View the redhat.repo file in /etc/yum.repos.d/ and verify that gpgkey is not set and gpgcheck is 0.
5. In katello, add a gpg key to the product.
6. On the client, run "subscription-manager refresh && yum repolist".
  

Actual results:

The gpgkey is set in redhat.repo but gpgcheck is still 0.


Desired results:

The gpgkey is set in redhat.repo but gpgcheck is 1.
Additional info:

Comment 2 RHEL Program Management 2012-12-14 08:47:05 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 Bryan Kearney 2013-02-22 20:44:56 UTC


*** This bug has been marked as a duplicate of bug 834125 ***