search

vmware-archive / cfops

This is simply an automation that is based on the supported way to back up Pivotal Cloud Foundry
http://www.cfops.io
Apache License 2.0
35 stars 24 forks source link

Problem restoring ops manager without microbosh #49

Closed aboik closed 8 years ago

aboik commented 8 years ago

Hi,

Can we restore an Ops Manager from the cfops backup when we do not have an existing micro-bosh deployment? After using the 'Delete this Installation' option in Ops Manager console and restoring the ops-manager tile with cfops and 'applying changes', I receive an error about a missing disk:

tarted deploy micro bosh > Updating persistent disk at depth 3 - 19: self signed certificate in certificate chain Started deploy micro bosh > Mount diskat depth 3 - 19: self signed certificate in certificate chain at depth 3 - 19: self signed certificate in certificate chain /home/tempest-web/tempest/web/vendor/bundle/ruby/2.2.0/gems/agent_client-1.3130.0/lib/agent_client/base.rb:21:in `method_missing': {"message"=>"Action Failed get_task: Task 0cf422cb-04ad-4f59-549a-c68d1d4ebe3d result: Persistent disk with volume id 'disk-9dd80515-b725-4c36-895f-6130e8e35e89' could not be found"} (Bosh::Agent::HandlerError)

After looking in the datastore, I confirmed that the disk does indeed exist.

Thanks, Drew

aboik commented 8 years ago

I noticed after trying unsuccessfully multiple times to restore the ops manager that there were left-over BOSH director VMs/disks running in vSphere from each unsuccessful restore. I cleaned these up and deployed a brand new ops manager of the same version as before, and it appears that the ops manager restore is working at this point, so I'm going to close this issue.