Bug 1577729 - MariaDB will raise an exception if value for Activity field_name is longer than 40 characters
Summary: MariaDB will raise an exception if value for Activity field_name is longer th...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 25.4
Assignee: Roman Joost
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-14 04:04 UTC by Roman Joost
Modified: 2018-05-24 22:52 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-24 22:52:48 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Beaker Project Gerrit 6098 0 None None None 2018-05-14 07:45:39 UTC

Description Roman Joost 2018-05-14 04:04:37 UTC
Description of problem:

The Activity is currently configured to support field_name values which are up to 40 characters long:

 field_name = Column(Unicode(40), nullable=False, index=True)

However, if MariaDB is configured with strict mode, inserting values longer than 40 characters results in an exception.

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

How reproducible:
100%

Steps to Reproduce:
1. Go to the systems page under InstallOptions
2. Add install options and choose a family with a very long name, kickstart metadata can be something short (e.g. foo=lol)

Alternatively, you can create a CSV import with a long ks_meta option and import that. See test_csv_import:CSVImportTest.test_double_quotes and it's associated CSV file.

Actual results:
SQLAlchemy tries to create an insert statement in which the field name is longer than 40 characters.

Expected results:
No exception.

Comment 1 Roman Joost 2018-05-18 06:22:00 UTC
We've realised a mistake with this bug in that we mistakenly released it with 25.3. In reflect of this change, I'll move it to 25.3 and close it.

Comment 2 Roman Joost 2018-05-18 07:05:57 UTC
On another look, it actually wasn't included. Mistake by me. My apologies. It's Friday.


Note You need to log in before you can comment on or make changes to this bug.