ansible-cmdb fails on certain host definitions. about ansible-cmdb

[fboender]

Hi Malcolm!

Thanks for the bug report!

I don't think it's an issue with your hosts file being too large. The "too many values to unpack" is kind of misleading in that regard ;-) Ansible is trying to parse one of the ranged hostnames (e.g. "foo[0:3].bar.com") and failing because it's expecting a colon.

Could you send your hosts file to my email address ([email protected]) so I can have a look at it? I will keep it completely confidential. If that's not an option, please let me know so I can figure out a different way to find out which hosts definition is causing the problem.

Regards,

Ferry

[mdmallardi]

Thank you for your help, this was indeed some issues with our inventory file. We've resolved these internally

[fboender]

Nice! Could you tell me what the issue was? I should probably skip hosts that fail instead of just failing altogether. At the very least ansible-cmdb should mention the host with the problem.

I'm going to change the title of this bug and reopen it so I can fix that.

[mdmallardi]

It was as you suspected:
we had host definitions like this:
d393sv-vmnginx[1:2], it was failing on those. When we split things out, it worked.

[mdmallardi]

Silly close button to the left, bad github, bad!

[fboender]

d393sv-vmnginx[1:2] is probably a valid host definition thought, right? ansible-cmdb should handle it properly than, so the bug report still is valid. I'll write up a fix soon. Thanks for your input Malcolm!

[mdmallardi]

Quite welcome! Yes, it is valid, but not widely in use in our environment.

[fboender]

I can't seem to reproduce the problem with a host definition of "d393sv-vmnginx[1:2]", but I get the same error if there is more than one pattern in the host definition (e.g. "db[0:2].app[0:2].foo.com"). Did you happen to have a host definition like this?

[mdmallardi]

I had a host definition more along the lines of:
d393sv-vmnginx[1:2:3], that may have set it off.

On Tue, Sep 22, 2015 at 1:56 PM, Ferry Boender [email protected]
wrote:

I can't seem to reproduce the problem with a host definition of
"d393sv-vmnginx[1:2]", but I get the same error if there is more than one
pattern in the host definition (e.g. "db[0:2].app[0:2].foo.com"). Did you
happen to have a host definition like this?

—
Reply to this email directly or view it on GitHub
#32 (comment)
.

Malcolm D. Mallardi

[fboender]

ansible-cmdb now shows an error on unparsable host definitions and skips them. Host definitions such as "db[0:2].app[0:2].foo.com" are properly expanded.