Project

General

Profile

Actions

Bug #6078

closed

-1 should not be used to represent "unlimited" for activation keys and host collections

Added by Walden Raines almost 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Web UI
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1105175
Description of problem:

Created a host-collection whose value was set to '10' for content-host limit. Later, I updated the limit with "-1", as soon as I type "-1", the text box closes and points to "unlimited" checkbox.

So -1 shouldn't be allowed for content host limit.

Version-Release number of selected component (if applicable):
sat6 beta snap8 (Satellite-6.0.3-RHEL-6-20140604.0)

How reproducible:
always

Steps to Reproduce:
1. create host collection with limit 10
2. update the limit with -1
3.

Actual results:
on updating the limit with -1, ticks the checkbox to unlimited

Expected results:
user shouldn't be allowed to set limit to -1

Additional info:
A related bz #848564


Related issues 1 (0 open1 closed)

Has duplicate Katello - Bug #6127: user shouldn't be allowed to update the content-host limit to -1 for selected host-colectionDuplicate06/09/2014Actions
Actions #1

Updated by Eric Helms almost 10 years ago

  • Assignee set to Walden Raines
  • Target version set to 45
  • Triaged set to Yes
Actions #2

Updated by Walden Raines almost 10 years ago

  • Has duplicate Bug #6127: user shouldn't be allowed to update the content-host limit to -1 for selected host-colection added
Actions #3

Updated by Eric Helms almost 10 years ago

  • Target version deleted (45)
Actions #4

Updated by Walden Raines almost 10 years ago

  • Subject changed from user shouldn't be allowed to update the content-host limit to -1 for selected host-colection to -1 should not be used to represent "unlimited"
  • Priority changed from Low to Normal
  • Target version set to 49

Changing summary this to reflect system-wide nature of problem.

For both activation keys and host collections we should not use -1 to represent "unlimited". This issue captures the following work:

  • Fix the client side UI so that only > 1 limits can be sent
  • Fix the server side so that "unlimited" is represented as a boolean and that limit is ignored if true
  • Check that candlepin integration still works
Actions #5

Updated by Walden Raines almost 10 years ago

  • Subject changed from -1 should not be used to represent "unlimited" to -1 should not be used to represent "unlimited" for activation keys and host collections
Actions #6

Updated by Walden Raines almost 10 years ago

  • Status changed from New to Assigned
Actions #7

Updated by Walden Raines almost 10 years ago

  • Status changed from Assigned to Ready For Testing
Actions #8

Updated by Walden Raines almost 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #9

Updated by Eric Helms over 9 years ago

  • translation missing: en.field_release set to 13
Actions

Also available in: Atom PDF