I think this patch added this wrong behavior [1]. Before this patch, the "_is_resource_deleted" [2] expected that the "func" returns the resource dict. The "_parse_body" returned the resource dict, extracting the first key. However, the [1] replaced by "rest_client.ResponseBody" which does not take the first key in account. As result, the "_is_resource_deleted" call of "res.get('status')" is returning None, instead of the "status" of the resource. The correct should be:
Possible soluton:
I think this patch added this wrong behavior [1]. Before this patch, the "_is_resource_ deleted" [2] expected that the "func" returns the resource dict. The "_parse_body" returned the resource dict, extracting the first key. However, the [1] replaced by "rest_client. ResponseBody" which does not take the first key in account. As result, the "_is_resource_ deleted" call of "res.get('status')" is returning None, instead of the "status" of the resource. The correct should be:
res['resource' ].get(" status" )
[1]https:/ /review. opendev. org/c/openstack /manila- tempest- plugin/ +/788248 /github. com/openstack/ manila- tempest- plugin/ blob/master/ manila_ tempest_ tests/services/ share/json/ shares_ client. py#L330
[2] https:/