Fixed error when --log is not specified

Details: * Fixed that not using the `--log` option resulted in an error message about invalid use of the `--log-comp` option. (issue #234) Signed-off-by: Andreas Maier <maiera@de.ibm.com>
zhmcclient · Sep 11, 2022 · acba085 · acba085
1 parent 2bec89a
commit acba085
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/docs/changes.rst b/docs/changes.rst
@@ -28,6 +28,9 @@ Released: not yet
 
 **Bug fixes:**
 
+* Fixed that not using the `--log` option resulted in an error message
+  about invalid use of the `--log-comp` option. (issue #234)
+
 **Enhancements:**
 
 **Cleanup:**

diff --git a/zhmc_prometheus_exporter/zhmc_prometheus_exporter.py b/zhmc_prometheus_exporter/zhmc_prometheus_exporter.py
@@ -221,7 +221,7 @@ def parse_args(args):
                         "({dests}). Default: no logging".
                         format(dests=', '.join(VALID_LOG_DESTINATIONS)))
     parser.add_argument("--log-comp", dest='log_complevels', action='append',
-                        metavar="COMP[=LEVEL]", default=[DEFAULT_LOG_COMP],
+                        metavar="COMP[=LEVEL]", default=None,
                         help="set a logging level ({levels}, default: "
                         "{def_level}) for a component ({comps}). May be "
                         "specified multiple times; options add to the default "