Wrong action_execution output evaluation using with-items

[Nikolay Makhotkin]

consider task the following:

get_volumes:
      with-items: id in <% $.volume_ids %>
      action: cinder.volumes_list
      input:
        search_opts: <% {"id" => $.id} + $.search_opts %>
      publish:
        volumes: <% task(get_volumes).result.where(len($) > 0).select({id => $[0].id, status => $[0].status}) %>
      on-success:
        - delete_all_volumes

$.volume_ids consist of 2 UUIDs, i.e == ["id1", "id2"]

Action execution objects: http://paste.openstack.org/show/616679/

But there are somehow merged outputs in each action execution: each one contains more than one volume. So I expected the following published variable in task:

[
  {
    "id": "id1",
    "status": "status1"
  },
  {
    "id": "id2",
    "status": "status2"
  }
]

But I got

[
  {
    "id": "id1",
    "status": "status1"
  },
  {
    "id": "id1",
    "status": "status1"
  }
]

Pay attention to id1/id2. Due to each action execution contains the same output (for 2 volumes) - I get only the first one for each and eventually they are the same.

UPD: The issue is related to YAQL. Somehow the expression <% {"id" => $.id + $.search_opts} %> where variable $.search_opts == {} resulted in {} (!!!) but should be {"id": $.id}. So volume list returned the whole volume list and therefore each action execution contains 2 volumes instead 1.

[Renat Akhmerov (rakhmerov)]

As I understand there's no issue in Mistral. It may be in YAQL. Nikolay, can you please add what you discovered?

[Nikolay Makhotkin (nmakhotkin)]

I investigated the problem and it seems that cinder.volumes_list doesn't process "id" search opt. And eventually I always get the whole volume list.