anchor.diff:  Found 1 problem
   
   Problem 1 of 1: VM with cloud ID `i-914c046a' missing.
  -  1. Ignore problem
  -  2. Recreate VM using last known apply spec
  -  3. Delete VM reference (DANGEROUS!)
  +  1. Skip for now
  +  2. Recreate VM
  +  3. Delete VM reference
   Please choose a resolution [1 - 3]: 3
   
   Below is the list of resolutions you've provided
   Please make sure everything is fine and confirm your changes
   
     1. VM with cloud ID `i-914c046a' missing.
  -     Delete VM reference (DANGEROUS!)
  +     Delete VM reference
   
   Apply resolutions? (type 'yes' to continue): yes
   Applying resolutions...
   
   Director task 624
  -  Started applying problem resolutions > missing_vm 168: Delete VM reference (DANGEROUS!). Done (00:00:00)
  +  Started applying problem resolutions > missing_vm 168: Delete VM reference. Done (00:00:00)
   
   Task 624 done
   
  
positive.code: 
  cck determined that `vol-549f071f` persistent disk is not attached to `i-4fcd99b4` VM. Possible options are:
  
  1. `Ignore`: the Director will not try to resolve this problem during 
  
  2. `Reattach disk to instance`: the Director will reattach persistent disk to the VM and mount it at its usual location `/var/vcap/store`. 
  
      Note on current behaviour: Release job processes will not be restarted when persistent disk is remounted.
  
  
negative.code: 
  Once the deployment is set via `bosh deployment` command you can simply run `bosh cck`. Here is an example output when no problems are detected:
  
  <pre class="terminal wide">
  $ bosh cck
  
  Performing cloud check...
  
  