Bug 1530649 - rhn-satellite-activate: Activation with RHN Classic Satellite Certificate is deprecated
Summary: rhn-satellite-activate: Activation with RHN Classic Satellite Certificate is ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Spacewalk
Classification: Community
Component: Installation
Version: 2.7
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jan Dobes
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space28
TreeView+ depends on / blocked
 
Reported: 2018-01-03 15:02 UTC by gmiguel
Modified: 2018-04-20 12:21 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-04 10:59:41 UTC
Embargoed:


Attachments (Terms of Use)

Description gmiguel 2018-01-03 15:02:17 UTC
Description of problem: I can't activate spacewalk with a new certificate using "rhn-satellite-activate".

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


How reproducible:
rhn-satellite-activate --sanity-only --rhn-cert=path_to_cert



Steps to Reproduce:
1.
2.
3.

Actual results:

"ERROR: Activation with RHN Classic Satellite Certificate is deprecated.
Please obtain a Manifest for this Satellite version via https://access.redhat.com/knowledge/tools/satcert, and re-run this activation tool with option --manifest=MANIFEST-FILE."

Expected results:

Successfully validation.

Additional info:

Comment 1 Jan Dobes 2018-01-04 10:59:41 UTC
Certificate activation is not supported in Spacewalk anymore. Spacewalk is using model from Satellite 5.8 and activates manifest ZIP generated with given subscriptions on Red Hat site instead.

Please note that for manipulating with Red Hat content cdn-sync tool is now used instead of satellite-sync tool. In Spacewalk, cdn-sync will allow to only sync specified CDN repositories to custom channel unless cdn-sync-mappings package is installed (available from subscribed Satellite 5.8 repository) - then it's possible to sync predefined channels.


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