Bug #76997 Command is async executed if --synchronous is set instead of --asynchronous

• Submitted: 11 May 2015 11:37
• Reporter: Alfranio Tavares Correia Junior
• Status: Won't fix
• Category: MySQL Fabric: Command-line
• Severity: S3 (Non-critical)
• Version: 1.5.1
• OS: Any
• CPU Architecture: Any

[11 May 2015 11:37] Alfranio Tavares Correia Junior

Description:
Commands are synchronously executed by default. However, some commands might be asynchronously executed for user convenience if the option --synchronous is provided:

  mysqlfabric group promote my_group --sycnhronous

This is not intuitive as --asynchronous is what anyone would expect though.

How to repeat:
Run any command that accepts the --sycnhronous option or check the code in lib/mysql/fabric/command.py

class Command(object):
    ...
    def generate_options(self):
        for opt, value in zip(reversed(cargs.args), reversed(cargs.defaults)):
           if type(value) is bool:
               if value:
                   action = "store_false"
               else:
                   action = "store_true"
           else:
               action = "store"

           command_option = {
               'options':["--" + opt],
               'dest':opt,
               'default':value,
               'action':action
           }
        ...

Suggested fix:
Rename the --synchronous to --asynchronous or make commands be executed asycnhronously by default.

[6 Jul 2017 19:19] Bugs System

Status updated to 'Won't fix' (Fabric is now covered under Oracle Lifetime Sustaining Support)