_bulk request with action.auto_create_index configured doesn't return the right bulk response

[ph]

Elasticsearch version: 5.3.0

Description of the problem including expected versus actual behavior:

When whitelisting index name using the action.auto_create_index and sending a bulk request to ES with a forbidden index name doesn't return the expected bulk response.

The response is missing a items fields, allowing us to check if each document succeeded or not

more details at logstash-plugins/logstash-output-elasticsearch#584

Steps to reproduce:

1. Adding the following to the elasticsearch.yml

 action.auto_create_index: .security,.monitoring*,.watches,.triggered_watches,.watcher-history*

2. using this json document.

cat /tmp/x
{"index":{"_id":null,"_index":".logstash-2017.04.08","_type":"stdin","_routing":null}}
{"@timestamp":"2017-04-09T10:34:25.253Z","@version":"1","host":"localhost.localdomain","message":"testing","type":"stdin"}

curl -D- --data-binary @/tmp/x localhost:9200/_bulk?pretty

HTTP/1.1 404 Not Found
Warning: 299 Elasticsearch-5.3.0-3adb13b "Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header." "Mon, 10 Apr 2017 19:46:17 GMT"
content-type: application/json; charset=UTF-8
content-length: 612

{
  "error" : {
    "root_cause" : [
      {
        "type" : "index_not_found_exception",
        "reason" : "no such index and [action.auto_create_index] ([.security,.monitoring*,.watches,.triggered_watches,.watcher-history*]) doesn't match",
        "index_uuid" : "_na_",
        "index" : ".logstash-2017.04.08"
      }
    ],
    "type" : "index_not_found_exception",
    "reason" : "no such index and [action.auto_create_index] ([.security,.monitoring*,.watches,.triggered_watches,.watcher-history*]) doesn't match",
    "index_uuid" : "_na_",
    "index" : ".logstash-2017.04.08"
  },
  "status" : 404
}

Tested in 5.1.2 returns a correct response:

% curl -D- --data-binary @/tmp/x localhost:9200/_bulk?pretty
HTTP/1.1 200 OK
content-type: application/json; charset=UTF-8
content-length: 496

{
  "took" : 0,
  "errors" : true,
  "items" : [
    {
      "index" : {
        "_index" : "logstash-2017.04.09",
        "_type" : "stdin",
        "_id" : null,
        "status" : 404,
        "error" : {
          "type" : "index_not_found_exception",
          "reason" : "no such index",
          "resource.type" : "index_expression",
          "resource.id" : "logstash-2017.04.09",
          "index_uuid" : "_na_",
          "index" : "logstash-2017.04.09"
        }
      }
    }
  ]
}

4. If in a single bulk request you target 2 different index, it will return a single bulk response in the bulk

Request

{"index":{"_id":null,"_index":".logstash-2017.04.08","_type":"stdin","_routing":null}}
{"@timestamp":"2017-04-09T10:34:25.253Z","@version":"1","host":"localhost.localdomain","message":"testing","type":"stdin"}
{"index":{"_id":null,"_index":".monitoring-2017.04.08","_type":"stdin","_routing":null}}
{"@timestamp":"2017-04-09T10:34:25.253Z","@version":"1","host":"localhost.localdomain","message":"testing 2","type":"stdin"}

Response:

{
  "error" : {
    "root_cause" : [
      {
        "type" : "index_not_found_exception",
        "reason" : "no such index and [action.auto_create_index] ([.security,.monitoring*,.watches,.triggered_watches,.watcher-history*]) doesn't match",
        "index_uuid" : "_na_",
        "index" : ".logstash-2017.04.08"
      }
    ],
    "type" : "index_not_found_exception",
    "reason" : "no such index and [action.auto_create_index] ([.security,.monitoring*,.watches,.triggered_watches,.watcher-history*]) doesn't match",
    "index_uuid" : "_na_",
    "index" : ".logstash-2017.04.08"
  },
  "status" : 404
}