RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

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.

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