Bug 970236 - The UID limits in node.conf are not enforced
Summary: The UID limits in node.conf are not enforced
Status: CLOSED UPSTREAM
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers   
(Show other bugs)
Version: 2.x
Hardware: Unspecified Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Rob Millner
QA Contact: libra bugs
URL:
Whiteboard:
Keywords: UpcomingRelease
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-03 19:07 UTC by Rob Millner
Modified: 2015-05-14 23:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-20 18:05:14 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Rob Millner 2013-06-03 19:07:11 UTC 
Description of problem:
The UID limits in node.conf are not enforced.  This leads to confusing behaviour.

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


How reproducible:
Occasionally in production, but easy to reproduce in dev by requesting a high UID.

Steps to Reproduce:
1. use oo-app-create and specify a high UID.

Actual results:
Succeeds.

Expected results:
Refused to create.

Additional info:
The production district code has a limit that's 1000 higher than the nodes.  Harmonize them as part of this bug.
Comment 1 Rob Millner 2013-06-03 19:13:01 UTC 
The port proxy allocator is based on the UID range and we've already had bugs with how the ranges conflict.
Comment 2 Rob Millner 2013-08-20 18:05:14 UTC 
Converted to a user story to cover the long standing technical debt.
https://trello.com/c/0MI9cZlv/247-the-node-and-broker-have-different-configuration-for-the-the-uid-limits
Note You need to log in before you can comment on or make changes to this bug.