Bug 1267910

Summary: PSQLException when insert value to audit log if input string is too long
Product: [oVirt] ovirt-engine Reporter: Ondra Machacek <omachace>
Component: AAAAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: bugs, gklein, iheim, masayag, mperina, oourfali
Target Milestone: ovirt-4.0.0-alphaFlags: rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
masayag: devel_ack+
pstehlik: testing_ack+
Target Release: 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt 4.0.0 alpha1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 12:54:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log none

Description Ondra Machacek 2015-10-01 11:29:02 UTC
Created attachment 1079052 [details]
engine.log

Description of problem:


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

How reproducible:
always

Steps to Reproduce:
1. Generate 247 chars long string (python -c 'print "A"*247')
2. into username field of webadmin login page insert this string a login

Actual results:
Action failed due to database connection failure. Please check connectivity to your Database server.

Expected results:
Login failed. Please verify your login information or contact the system administrator.

Additional info:

Comment 1 Alon Bar-Lev 2015-10-01 14:56:24 UTC
not sure this should not be generic error, just like any other internal command error.

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-19 10:53:34 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Gil Klein 2016-07-27 12:54:26 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA