Bug #74458 Setup doesn't work
Submitted: 20 Oct 2014 13:56 Modified: 27 Oct 2014 14:46
Reporter: Anthony Regeda Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Fabric Severity:S1 (Critical)
Version:>1.5.2 OS:Linux (Ubuntu 14.04)
Assigned to: CPU Architecture:Any
Tags: configuration, fabric

[20 Oct 2014 13:56] Anthony Regeda
Description:
After "mysqlfabric manage setup" I get SQL errors.

How to repeat:
I test mysqlfabric on vargant instance (https://github.com/regeda/vagrant-mysqlfabric)

After "mysqlfabric manage setup" I get:

[INFO] 1413812933.632639 - MainThread - Initializing persister: user (fabric), server (localhost:3306), database (fabric).
Error: Command (CREATE TABLE providers (provider_id VARCHAR(256) NOT NULL, type INT NOT NULL, username VARCHAR(100) NOT NULL, password VARCHAR(128) NOT NULL, url VARCHAR(256) NOT NULL, tenant VARCHAR(100) NOT NULL, default_image VARCHAR(256), default_flavor VARCHAR(256), CONSTRAINT pk_provider_id PRIMARY KEY (provider_id)), ()) failed accessing (localhost:3306). 1071 (42000): Specified key was too long; max key length is 767 bytes.

Then I set the option "innodb_large_prefix" to "ON" and get following:

[INFO] 1413813147.801432 - MainThread - Initializing persister: user (fabric), server (localhost:3306), database (fabric).
Error: Command (CREATE TABLE machines (machine_uuid VARCHAR(40) NOT NULL, provider_id VARCHAR(256) NOT NULL, av_zone VARCHAR(256), addresses TEXT, INDEX idx_machine_provider_id (provider_id)), ()) failed accessing (localhost:3306). 1709 (HY000): Index column size too large. The maximum column size is 767 bytes..

Suggested fix:
Mysqlfabric manager should create a configuration on a server.
I think the bug in a big varchar length for "provider_id" in both cases.
[22 Oct 2014 6:46] Mahesh Patil
I am also getting same error on Centos 6.3. Please fix on priority.
[27 Oct 2014 14:46] Mats Kindahl
Thank you for the bug report. I agree that this should work without problems. This bug is a duplicate of BUG#74192.