Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1122901

Summary: PGError when architecture name exceeds 255 characters
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: WebUIAssignee: orabin
WebUI sub component: Foreman QA Contact: Katello QA List <katello-qa-list>
Status: CLOSED DUPLICATE Docs Contact:
Severity: low    
Priority: unspecified CC: bkearney, cwelton, dcleal
Version: 6.0.4Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/6658
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-29 16:47:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1120271    
Bug Blocks:    
Attachments:
Description Flags
PgError when arch name exceeds 255 characters none

Description Sachin Ghai 2014-07-24 10:56:47 UTC
Created attachment 920501 [details]
PgError when arch name exceeds 255 characters

Description of problem:
I was trying to perform boundary test are created a new architecture with more than 255 characters in name and UI raises following error:

Error
PGError: ERROR: value too long for type character varying(255) : INSERT INTO "architectures" ("created_at", "hostgroups_count", "hosts_count", "name", "updated_at") VALUES ($1, $2, $3, $4, $5) RETURNING "id"


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

How reproducible:
always

Steps to Reproduce:
1. create arch with name more 255 char
2.
3.

Actual results:
Error
PGError: ERROR: value too long for type character varying(255) : INSERT INTO "architectures" ("created_at", "hostgroups_count", "hosts_count", "name", "updated_at") VALUES ($1, $2, $3, $4, $5) RETURNING "id"

Expected results:
A proper validation error should be raised.


Additional info:
Processing by ArchitecturesController#create as */*
  Parameters: {"utf8"=>"✓", "search"=>"", "authenticity_token"=>"XLkNroe/1GYA+eEExa2V5ge+6IRgFtgTIMEwhb4GycY=", "architecture"=>{"name"=>"ojJELjrEfavaKHSkSDTncoiqjwik12345yyteyNSBmqcshsFlNcAsGExwayeTXjFOQmXTuVNWCotNUBMbiJmDKtsPtLnXqYJSjTUyNIlSNAAucqVkKXGFrViwyGLTRnqqBaLuGskexxWkYHTLHdLFMEXTmRLiGZgvkTGGmqGEKpGwzEOerEAbVJWBLaKytzydTwJcIQOUdBxowqKqIUSJKZkYHwUzkPWGjQMkpdpadzBctjvjBMDmpfPYurKybz1", "operatingsystem_ids"=>[""]}}
Operation FAILED: PGError: ERROR:  value too long for type character varying(255)
: INSERT INTO "architectures" ("created_at", "hostgroups_count", "hosts_count", "name", "updated_at") VALUES ($1, $2, $3, $4, $5) RETURNING "id"
  Rendered common/500.html.erb (7.1ms)
Completed 500 Internal Server Error in 166ms (Views: 9.7ms | ActiveRecord: 2.6ms)

Comment 1 Dominic Cleal 2014-07-24 11:02:39 UTC
Thanks, we're collecting lots of near-identical BZs, please just add them to bug #1120271 in future.

Comment 3 Sachin Ghai 2014-07-24 11:24:45 UTC
@Dominic: Sure. I'll update  bug #1120271, if found similar bz with any other entity. Thank you for quickly ack'ing all such bugs.

Comment 4 Bryan Kearney 2014-07-29 16:47:35 UTC
The same fix for 1120095 fixes this as well. Please treat these as duplicates.

*** This bug has been marked as a duplicate of bug 1120095 ***