Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 874488

Summary: PGError: ERROR: value too long for type character varying(1024) :when given long name for "Cloud resource cluster"name
Product: [Retired] CloudForms Cloud Engine Reporter: Rehana <redakkan>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Giulio Fidente <gfidente>
Severity: low Docs Contact:
Priority: low    
Version: 1.1.0CC: gfidente
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 17:59:04 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:
Attachments:
Description Flags
rails none

Description Rehana 2012-11-08 10:08:07 UTC 
Description of problem:


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


How reproducible:
100%

Steps to Reproduce:
1.Login to conductor
2.Move to Administer -->Content--> new cloud resource cluster
3.Give very long name for the cluster
  
Actual results:
Observations made are:

1.when given a very long name for the Cluster,it throws PG error
2.Also the cluster name accepts special characters 

Expected results:
1.The cluster name field should be limited to say 50
2.the name field should not accept special characters

Additional info:
rpm -qa | grep aeolus
aeolus-conductor-0.13.24-1.el6cf.noarch
aeolus-conductor-daemons-0.13.24-1.el6cf.noarch
rubygem-aeolus-cli-0.7.7-1.el6cf.noarch
aeolus-conductor-doc-0.13.24-1.el6cf.noarch
aeolus-configure-2.8.11-1.el6cf.noarch
aeolus-all-0.13.24-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
Comment 1 Rehana 2012-11-08 10:08:48 UTC 
Created attachment 640707 [details]
rails
Comment 3 Giulio Fidente 2012-11-15 14:04:05 UTC 
I don't see this as a bug, shall we close it as NOTABUG?
Comment 4 Rehana 2012-11-16 04:36:31 UTC 
hi Giulio,

I m still able to reproduce this bug.You can reproduce it buy giving a very long name
Comment 5 Giulio Fidente 2012-11-16 09:05:13 UTC 
sure, I'm not saying that there is no limit but I don't think that having a limit on the lenght of the string is a bug