Bug #71793 MysqlFabric wrong error messages from dump cmd when shard doesnt exist

• Submitted: 21 Feb 2014 20:28
• Modified: 24 Apr 2014 13:46
• Reporter: Andres Eduardo Sanchez Rodriguez
• Status: Closed
• Category: MySQL Fabric
• Severity: S3 (Non-critical)
• Version: 1.4.0
• OS: Linux (2.6.39-200.24.1.el6uek.x86_64)
• Assigned to: Mats Kindahl
• CPU Architecture: Any

[21 Feb 2014 20:28] Andres Eduardo Sanchez Rodriguez

Description:
Wrong messages are prompted after executing sharding and dump commands when no Shard exists:

bash-4.1$ mysqlfabric dump shard_tables
 option --version: conflicting option string(s): --version

How to repeat:
Create HA setup, then try to use dump commands, without adding a shard definition:

-bash-4.1$ mysqlfabric help dump shard_tables
dump shard_tables  [--VERSION=NONE] [--PATTERNS=]  

Return information about all tables belonging to mappings matching
any of the provided patterns. If no patterns are provided,dump
information about all tables.

-bash-4.1$ mysqlfabric dump shard_tables
option --version: conflicting option string(s): --version
-bash-4.1$ mysqlfabric dump shard_maps
option --version: conflicting option string(s): --version
-bash-4.1$ mysqlfabric dump servers
option --version: conflicting option string(s): --version
-bash-4.1$ mysqlfabric dump shard_tables --VERSION
option --version: conflicting option string(s): --version
-bash-4.1$ mysqlfabric dump shard_tables --VERSION=NONE
option --version: conflicting option string(s): --version
-bash-4.1$ mysqlfabric dump shard_tables --version=none
option --version: conflicting option string(s): --version

[24 Feb 2014 11:17] Mats Kindahl

Thank you for the bug report. Verified as described.

[24 Apr 2014 13:46] Daniel So

Added the following entry to the MySQL Utilities 1.4.2 changelog:

"The mysqlfabric utility returned wrong messages for dump commands when no shards exist."