Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Bug 1311846 - OS release version not attached to a copied Activation Key correclty
Summary: OS release version not attached to a copied Activation Key correclty
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.1.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-25 07:53 UTC by Frank Reimer
Modified: 2017-08-04 13:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-04 13:19:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Frank Reimer 2016-02-25 07:53:42 UTC 
Description of problem:
I`ve created an Activation Key and attached a "Release Version" on the Details tab to the Activation Key. I also configured all other needed things like product content, subscriptions and so on. 

If I now copy this Activation Key the Release Version seems to be present at the copied Activation Key. But when I try to install a new client with the copied Activation Key which for example has 7.2 as a release version then the client does not configure the release version via subscription-manager correctly during provisioning. This leads to the problem that the client is not able to access the correct RHEL Yum repositories on Satellite.

If I open the copied Activation Key again, delete the release version and attach the release version again, then the client can successfully access all needed Yum repositories with this specific release version during provisioning. 

Version-Release number of selected component (if applicable):
- Satellite 6.1.6
- RHEL 7.2

How reproducible:
- Copy an Activation Key with "Release Version" configured.

Steps to Reproduce:
1. Copy an Activation Key with "Release Version" configured.
2. Do not change anything regarding "Release Version"


Actual results:
The release version seems to be configured at the copied Activation Key without taking effect.

Expected results:
If an activation key will be copied then I expect every parameter configured at the parent activation key will also be configured correctly at the copied activation key without any manual interventions. 

Additional info:
Comment 2 Bryan Kearney 2016-07-26 19:03:33 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 3 Bryan Kearney 2017-08-04 13:19:04 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Note You need to log in before you can comment on or make changes to this bug.