This is a bug in the API which appears to have been fixed this morning in the latest 1.9.x series trunk for the 2.0 release. I know I have been saying this for a while but I am nearing the completion of the next release for Zabcon, the challenge is getting the 6-12(ish) hours needed.
Unfortunately right now the error can mean either that your api call is incorrect or you don't have permissions.
From the zabcon help file:
{{{
Required arguments:
host, port, ip and/or dns, status, proxy_hostid, groups, useip
Optional arguments:
available, disable_until, status, templates, maintenance, maintenance_from, maintenance_status, maintenance_type, useipmi, ipmi_authtype, ipmi_available, ipmi_disable_until, ipmi_errors_from, ipmi_ip, ipmi_password, ipmi_port, ipmi_privilege, ipmi_username, snmp_available, snmp_disable_until, snmp_errors_from, outbytes, error, lastaccess, errors_from, inbytes
}}}
try adding useip=false to your host create.
Unfortunately right now the error can mean either that your api call is incorrect or you don't have permissions.
From the zabcon help file:
{{{
Required arguments:
host, port, ip and/or dns, status, proxy_hostid, groups, useip
Optional arguments:
available, disable_until, status, templates, maintenance, maintenance_from, maintenance_status, maintenance_type, useipmi, ipmi_authtype, ipmi_available, ipmi_disable_until, ipmi_errors_from, ipmi_ip, ipmi_password, ipmi_port, ipmi_privilege, ipmi_username, snmp_available, snmp_disable_until, snmp_errors_from, outbytes, error, lastaccess, errors_from, inbytes
}}}
try adding useip=false to your host create.
Comment