thanks for the quick fix! I can confirm that now it works perfect :) While testing I also noticed another small issue and I created an issue in github https://github.com/gc3-uzh-ch/elasticluster/issues/341
I don't think it's a big issue but if users don't notice it they can get higher bills when using elasticluster. regards, Pablo. 2016-11-11 15:36 GMT+01:00 Riccardo Murri <[email protected]>: > Hi Pablo, > > On 11 November 2016 at 14:32, Pablo Escobar <[email protected]> wrote: > > RUNNING HANDLER [iptables : reload iptables] > > *********************************** > > fatal: [compute001]: FAILED! => {"failed": true, "msg": "the field 'args' > > has an invalid value, which appears to include a variable that is undefi > > ned. The error was: 'ansible.parsing.yaml.objects.AnsibleUnicode > object' has > > no attribute u'Debian'\n\nThe error appears to have been in '/opt/ela > > sticluster/src/elasticluster/share/playbooks/roles/ > iptables/handlers/main.yml': > > line 3, column 3, but may\nbe elsewhere in the file depending on t > > he exact syntax problem.\n\nThe offending line appears to be:\n\n\n- > name: > > reload iptables\n ^ here\n"} > > another bug :) -- I had changed the structure of the `iptables` role > before, and forgot > to update the handler. > > Should be fixed in commit 31a33df > > Thanks for reporting! > > Ciao, > R > -- You received this message because you are subscribed to the Google Groups "elasticluster" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
