Cisco CBS350 command Time-Out due to NO newline after command output about community.ciscosmb

[ecleese]

Thanks for figuring this out. This fix worked for me to run multiple commands but breaks the facts module. If I run the example ciscosmb_gather_facts.yml playbook I get the following error with the above fix in place:

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: 'NoneType' object has no attribute 'groupdict'

If I revert the change back the ciscosmb_gather_facts.yml successfully runs. Any ideas why this would happen?

[qaxi]

... but breaks the facts module. If I run the example ciscosmb_gather_facts.yml playbook I get the following error with the above fix in place:

Is that problem CSB specific, or general ? I tested it on CSB a other SG an I have not souch issue.

[AndreiSucu]

Thanks for figuring this out. This fix worked for me to run multiple commands but breaks the facts module. If I run the example ciscosmb_gather_facts.yml playbook I get the following error with the above fix in place:

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: 'NoneType' object has no attribute 'groupdict'

If I revert the change back the ciscosmb_gather_facts.yml successfully runs. Any ideas why this would happen?

I have tested this in my environment on a CBS 350-24TX Version: 3.1.1.7 and I did not notice any issues, the gather_facts task runs okay for all subsets with or without the change mentioned above.

Example task that works:

• name: Collect only the config and default facts
  community.ciscosmb.facts:
  gather_subset:
  - config

Some off-topic info, there are substantial differences between the CBS 220 and 350, for example.
On 220 the gather_facts module does not work entirely due to the hardcoded commands built into the "facts.py" module.

Normal behavior of course, just wanted to point it out.

[ecleese]

We only use 350 series switches. I've only tested on two CBS350-24P-4G (fw v3.3.0.16) switches so far but both fail using the gather_facts module with the error I posted when this fix is applied. I'm not sure what could be different in my instance compared to yours and qaxi. I try and do some more testing next week.