Bug 702385

Summary: User with expired system subscription can still register a new system
Product: [Community] Candlepin Reporter: Lisa Lu <llu>
Component: candlepinAssignee: Bryan Kearney <bkearney>
Status: CLOSED NOTABUG QA Contact: John Sefler <jsefler>
Severity: high Docs Contact:
Priority: unspecified    
Version: 0.5   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-11 18:46:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 568421    
Attachments:
Description Flags
screen shote of the overview page of an user with expired system sub none

Description Lisa Lu 2011-05-05 14:21:15 UTC
Created attachment 497109 [details]
screen shote of the overview page of an user with expired system sub

Description of problem:
login "laboproba" has expired system subscriptions according to this doc:
 https://docspace.corp.redhat.com/docs/DOC-56650

After login as this user, I can still register a new system.

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


How reproducible:
Very

Steps to Reproduce:
1. https://avalon-ci.gss.redhat.com/management/
2. login as: laboproba/redhat
3. click on "Register a new system" hotlink
  
Actual results:
 user with expired system subscription can still register a new system

Expected results:
 user with expired system sub CAN NO LONGER register a new system
 
Additional info:

Comment 1 John Sefler 2011-05-10 17:19:11 UTC
I don't believe the ability to register a new system has any dependency on expired subscriptions on a different system.  When a subscription on a system expires, it simply means that system is no longer entitled to the rights to the service or bits (package data) that the subscription was providing to the system.

Maybe I am not understanding the error being reported here...