Missing disk inside the vRA deployments.
Due to missing deployment resource, any 2nd day operation cannot be done as Deployment is in unhealthy state.
Deployments are coming from Google Cloud Platform (GCP) account.
When check the catalog-db database, there are "Missing" disks and also disk with the same name and attributes marked as "DISCOVERED"
In order to KB be applicable, the pair of the disk must exist in the catalog-db, one must be (DEPLOYED, MISSING) and second must be (DISCOVERED, SUCCESS)
In this case, we the Missing disk named "disk3-testMachine-00001"
catalog-db=# select id,name,provider_resource_name,summary_properties,type,origin,state,sync_status from dep_resource where CAST (summary_properties as TEXT) like '%disk3-testMachine-00001%'; id | name | provider_resource_name | summary_properties | type | origin | state | sync_status--------------------------------------+------------------------------------------+------------------------------------------+--------------------------------------------------------------+----------------+------------+-------+------------- BBBBBBBB-BBBB-BBBB-BBBB-BBBBBBBBBBBB | disk3 | disk3-testMachine-00001 | {"resourceName": "disk3-testMachine-00001"} | Cloud.GCP.Disk | DEPLOYED | OK | MISSING AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA | disk3-testMachine-00001 | disk3-mcm18415-250450132409-515308561871 | {"resourceName": "disk3-testMachine-00001"} | Cloud.GCP.Disk | DISCOVERED | OK | SUCCESS
Aria Automation 8.18
In order to fix the binding between machines and disks, please raise the ticket with support team.