Bug 56235

Summary:	Show Stopper!! Up2date doesn't understand enterprise entitlements
Product:	[Retired] Red Hat Network	Reporter:	Jay Turner <jturner>
Component:	RHN/Backend	Assignee:	Jay Turner <jturner>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jay Turner <jturner>
Severity:	high	Docs Contact:
Priority:	high
Version:	RHN Devel	CC:	cturner, gafton, mihai.ibanescu, pjones, srevivo, taw
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-03-07 18:33:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jay Turner 2001-11-14 13:41:13 UTC

Description of Problem:
If you run up2date on a system which has an enterprise entitlement as
opposed to a personal entitlement, then you will get error code 31 (system
not entitled.)

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


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Peter Jones 2001-11-14 16:36:00 UTC

I'm not exactly sure who's bug this is.  The question is this: If all enterprise
entitlements are also supposed to provide "update assistant" functionality, why
don't we just make the product provide one of each?

I was told not to do this, of course, but it may still be the right answer...

Comment 2 Adrian Likins 2001-11-14 17:10:26 UTC

what exactly is it that the client should be doing different in this case?

I'm not aware of any difference in the way system ids are created for
enterprise setups or otherwise.

Comment 3 Cristian Gafton 2001-11-14 18:14:14 UTC

this is teh server side - I am looking explicitly for the label of the software
manager service

might be usefull to hack in some sort of mapping that for each groupid that is
used in entitlement we add a flag that tells us whether up2date is functioning
or not - or figure out how to implement roles.

right now looks like we have three services that are being provided: Software
manager, update assistant and Systems Manager. As we add more we'll need to be
able to qualify those roles somehow.

Comment 4 Jay Turner 2001-11-14 19:07:42 UTC

Changing this to the correct component.

Comment 5 Greg DeKoenigsberg 2001-11-27 21:46:16 UTC

In the web code, the standard emerging method for telling if a system is
viewable is to see if the entitlement check returns "none" or not.

As entitlements change, I'm guessing that the one constant rule will be this:
any system that is in *any* way entitled to RHN will be entitled to receive
updates.  Therefore, the "none" check should remain valid in all cases.

Comment 6 Greg DeKoenigsberg 2001-12-18 17:18:16 UTC

Jay, has this bug been closed?

Comment 7 Greg DeKoenigsberg 2002-03-07 18:33:29 UTC

This bug could not possibly still be open.

Comment 8 Jay Turner 2002-05-15 12:46:12 UTC

Indeed, this has been fixed for quite some time.  Closing out.