Cudet fails to run with custom configuration file

[Dmitriy Kruglov]

Detailed bug description:
Cudet tool fails on an attempt to apply custom nodes filters (by role, ID, etc.) via custom configuration file.
The issue also occurs when specifying default config file (/usr/share/cudet/cudet-config.yaml one) as the config to use.

Steps to reproduce:
1 Deploy a 9.x cluster (e.g. from snapshot)
2 Install Cudet
  yum install -y python-cudet
3 Copy /usr/share/cudet/cudet-config.yaml Cudet config file to a local working directory
4 Run the tool specifying config file to use
  cudet -c ./cudet-config.yaml

Expected result: the tool is executed according to filter parameters specified in the config file.
Actual result: error occurs with the following trace

[root@nailgun ~]# cudet --config cudet-config.yaml
2016-09-07 08:20:37,558 CRITICAL (nodes) NodeManager: directory %s does not exist
There are no nodes to check
2016-09-07 08:20:37,560 ERROR (utils) Error: unsupported operand type(s) for %: 'NoneType' and 'str'
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/cudet/utils.py", line 37, in wrapper
    f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/cudet/main.py", line 497, in main
    raise e
TypeError: unsupported operand type(s) for %: 'NoneType' and 'str'

[Anton Samoylov (asamoylov)]

Hello Dmitriy,
Did you change 'rqdir', 'rqfile' and 'cudet_db_dir' to actual values in local config file ?

[Dmitriy Kruglov (dkruglov)]

Hi Anton,
Thank you for the update. You are right, I used cudet in the directory other than /usr/share/cudet/ one, which is referenced by those parameters in case of default config file.
It was not straightforward from the description of cudet tool which config parameters are mandatory for update in case of custom configuration.

I tried the tool with custom config appropriately and it produces the expected result. SO I mark the issue as invalid.