← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2012944] [NEW] neutron-remove-duplicated-port-bindings does not write to stdout

 

Public bug reported:

The new neutron-remove-duplicated-port-bindings tool does not log any
information when run from the CLI, as the log levels are mismatching.

The logger gets initialized with log_level = WARNING, but the tool uses LOG.info() to display its messages, therefore the user never receives any results.
Furthermore, the logger does not take into account any parameters from the neutron config file during its initialization, and instead relies on its default settings, so log-related settings (log-level, log-path, etc.) cannot be changed.

On another note, dry-running is only possible when setting [cli_script] dry_run=True in the neutron config file, which is inconvenient to say the least.
A proper --debug CLI option would be way more helpful.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2012944

Title:
  neutron-remove-duplicated-port-bindings does not write to stdout

Status in neutron:
  New

Bug description:
  The new neutron-remove-duplicated-port-bindings tool does not log any
  information when run from the CLI, as the log levels are mismatching.

  The logger gets initialized with log_level = WARNING, but the tool uses LOG.info() to display its messages, therefore the user never receives any results.
  Furthermore, the logger does not take into account any parameters from the neutron config file during its initialization, and instead relies on its default settings, so log-related settings (log-level, log-path, etc.) cannot be changed.

  On another note, dry-running is only possible when setting [cli_script] dry_run=True in the neutron config file, which is inconvenient to say the least.
  A proper --debug CLI option would be way more helpful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2012944/+subscriptions



Follow ups