Bug 702385 - User with expired system subscription can still register a new system
Summary: User with expired system subscription can still register a new system
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 0.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Bryan Kearney
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: 568421
TreeView+ depends on / blocked
 
Reported: 2011-05-05 14:21 UTC by Lisa Lu
Modified: 2015-05-14 15:21 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-11 18:46:43 UTC


Attachments (Terms of Use)
screen shote of the overview page of an user with expired system sub (162.52 KB, image/png)
2011-05-05 14:21 UTC, Lisa Lu
no flags Details

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...


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