Nerijus Baliūnas
Nerijus Baliūnas
But it is not fine, we still get exceptions like in the 1st post, although all our hostnames are less than 255. Are you telling that it should work even...
I just tested with #437 , it is ok now, I don't get exceptions anymore. Thanks!
I reported it last year - https://github.com/ansible-collections/community.general/pull/3093#issuecomment-954695152
We have the same problem.
Should be fixed with upcoming amazon.aws release.
I updated to svn trunk and do not get this error on CentOS 7 anymore, but do get it on Fedora 21. It's bare metal, a few VM's created with...
After the host reboot I got this error on CentOS 7 again too.
I cannot start firewalld, because I use another firewall (shorewall). I have 8001 tcp port opened from outside. I added 8000 too, but it did not help.
Is it possible for kimchid to not try to start networks? Because I use libvirt, and everything (including VMs) is started by libvirtd when the host boots.
/etc/libvirt/qemu/networks/default.xml: ``` default ee499638-e505-4fcc-8722-26b78ac69fb1 ```