Bug 1401519 - Request-URI Too Long on accessing architecture with name too long
Summary: Request-URI Too Long on accessing architecture with name too long
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-05 13:46 UTC by Roman Plevka
Modified: 2017-12-19 14:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-10 12:36:14 UTC
Target Upstream Version:

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

Description Roman Plevka 2016-12-05 13:46:23 UTC 
Description of problem:
There seems to be no name-length limit for Architectures.
Creating with name too long logically triggers Request-URI too long (since its name is appended to the url as a part of the GET request)

the same issue is reproducible using CLI when --name is used. (or API with applying search by name).


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
no length limit for architecture name

Expected results:
length restriction takes place (max 255 chars as for other entities)

Additional info:
Comment 1 Roman Plevka 2016-12-05 13:47:40 UTC 
version: 6.3.0 snap6
Comment 6 Bryan Kearney 2017-12-19 14:57:56 UTC 
setting flag based on request from Og to kick off automation.
Note You need to log in before you can comment on or make changes to this bug.