Steps to reproduce:
1.Create a plan use 'OS Infra Provider with volume snapshot plugin':
karbor plan-create 'OS volumes protection plan.' 90d5bfea-a259-41e6-80c6-dcfcfcd9d827 'a7da2a52-7e66-437c-9394-e391150b6dd0'='OS::Cinder::Volume'='volume2'
2.Create a checkpoint use the plan：
karbor checkpoint-create 90d5bfea-a259-41e6-80c6-dcfcfcd9d827 d0e69bdb-e213-45fa-832c-7933bd21ee48
3.After the volume snapshot create successfully, restore from it:
karbor restore-create 90d5bfea-a259-41e6-80c6-dcfcfcd9d827 5f9e0ab3-6c23-489b-8038-0e4d2ca87bcc
4.Query the result, the resources_status is always be 'creating' even if restore is successfully.
# karbor restore-show 2bfff44f-27ca-43d4-a213-eaab115da229
+------------------+---------------------------------------------------------------------------+
| Property | Value |
+------------------+---------------------------------------------------------------------------+
| checkpoint_id | eb393c9f-9c0d-48fc-a14b-57b097ad3672 |
| id | 2bfff44f-27ca-43d4-a213-eaab115da229 |
| parameters | { |
| | "OS::Cinder::Volume": { |
| | "restore_description": null, |
| | "restore_name": null |
| | } |
| | } |
| project_id | 65b4ae220623472194a162d519eb2080 |
| provider_id | 90d5bfea-a259-41e6-80c6-dcfcfcd9d827 |
| resources_reason | {} |
| resources_status | {u'OS::Cinder::Volume#981fb659-25de-49b3-84ad-4b763aa211f1': u'creating'} |
| restore_target | None |
| status | success |
+------------------+---------------------------------------------------------------------------+
The resources_status should be the same as the volume's status.
Fix proposed to branch: master
Review: https:/