Bug 464244 - add supporting functionality on the server side for registration eus options to work with activationkeys
Summary: add supporting functionality on the server side for registration eus options ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Registration
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Clifford Perry
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714 479461
TreeView+ depends on / blocked
 
Reported: 2008-09-26 20:38 UTC by Pradeep Kilambi
Modified: 2014-05-09 10:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-09 10:39:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pradeep Kilambi 2008-09-26 20:38:45 UTC
Description of problem:

Currently server doesn't support use of --use-eus-channel option in conjunction with --activationkey, while registering as the supporting functionality is not implemented on the server. We raise an exception on the client to use the username and password instead. It would be nice to get this functionality implemented so users could use activationkey when using --use-eus-channel option.

So basically available_eus_channels method needs username and password now in registration.py. We need another equivalent method in case activationkey is specified.


This change needs to be ported to hosted only we have it working on satellites.

Comment 1 Pradeep Kilambi 2008-09-26 20:43:28 UTC
This change needs to be ported to hosted only we have it working on satellites.

should read:

This change needs to be ported to hosted once we have it working on satellites.

Thanks,

Comment 2 Brandon Perkins 2008-10-01 19:06:55 UTC
Agreed.  And when we get the code, this bug should be cloned for Hosted.

Comment 17 Clifford Perry 2014-05-09 10:39:20 UTC
We have not addressed this specific bug in over 5 years years. This does not seem to have an active customer case with the bug report either. Closing out as wontfix to clear from backlog. 

Please re-open if you disagree and wish further review.

Cliff


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