[dev.icinga.com #8869] Array in command arguments doesn't work

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/8869

Created by gbeutner on 2015-03-26 08:29:23 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2015-03-26 08:44:54 +00:00)
Target Version: 2.3.3
Last Update: 2015-03-26 08:44:54 +00:00 (in Redmine)

Icinga Version: 2.3.2
Backport?: Already backported
Include in Changelog: 1

---

Changesets

2015-03-26 08:29:52 +00:00 by (unknown) 3adec45

Fix arrays in command arguments

fixes #8869

2015-03-26 08:44:47 +00:00 by (unknown) 47e17bf

Fix arrays in command arguments

fixes #8869

[icinga-migration]

Updated by mfriedrich on 2015-03-26 08:30:07 +00:00

<9> =>  s = get_servis.last_check_result
{
    "active": true,
    "check_source": "nbmif.int.netways.de",
    "command": [
        "/usr/lib64/nagios/plugins/check_dummy",
        "0",
        [
            "windows-servers",
            "linux-servers",
            "linux-servers-test"
        ]
    ],
    "execution_end": 1427357691.6432819366,
    "execution_start": 1427357691.6410870552,
    "exit_status": 0.0,
    "output": "OK: Object of type 'icinga::Array'",
    "performance_data": [

    ],
    "schedule_end": 1427357691.6434690952,
    "schedule_start": 1427357696.6400001049,
    "state": 0.0,
    "type": "CheckResult",
    "vars_after": {
        "attempt": 1.0,
        "reachable": true,
        "state": 0.0,
        "state_type": 1.0
    },
    "vars_before": {
        "attempt": 1.0,
        "reachable": true,
        "state": 0.0,
        "state_type": 1.0
    }
}

[icinga-migration]

Updated by Anonymous on 2015-03-26 08:30:21 +00:00

• Status changed from New to Resolved
• Done % changed from 0 to 100

Applied in changeset 3adec45.

[icinga-migration]

Updated by mfriedrich on 2015-03-26 08:35:41 +00:00

• Status changed from Resolved to Assigned
• Target Version changed from 2.4.0 to 2.3.3
• Backport? changed from TBD to Yes

[icinga-migration]

Updated by Anonymous on 2015-03-26 08:44:54 +00:00

• Status changed from Assigned to Resolved

Applied in changeset 47e17bf.