Bug 1368857 - Satellite 6 activation_key
Summary: Satellite 6 activation_key
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: system-config-kickstart
Version: 6.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Chris Lumens
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-21 22:38 UTC by Paul
Modified: 2017-12-06 12:00 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:00:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Paul 2016-08-21 22:38:02 UTC
Description of problem:
Durint post install we are not properly getting the kickstart repo for satellite. Saying repo not valid. The subscription manager also cannot subscribe. But after a while it registered to subscription manager but without still without the satellite repo.

My question is the activation key should be unique per hostgroup? Because 2 of the hostgroup has the same activation keys. The repos its getting is from the last created hostgroup which acquired the the same activation key as the other one. Is that the possile cause?

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Jan Kurik 2017-12-06 12:00:05 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.