Operations Manager Install or Updates error "Could not find VM for stemcell xxxxx"

Products

• Operations Manager

Issue/Introduction

Symptoms:

When attempting to install or update a new tile, the error message "Could not find VM for stemcell" is seen.

For example:

Started compiling packages > jq/13de655de2512a47349a30f4577e05b201f8f811. Failed: Unknown CPI error 'Unknown' with message 'Could not find VM for stemcell 'sc-xxxxxxxxxxxxxxx'' (00:00:03)

Error 100: Unknown CPI error 'Unknown' with message 'Could not find VM for stemcell 'sc-xxxxxxxxxxxxxxx''

Task 6119 error

Environment

Resolution

Run 'BOSH Stemcells' to get a list of all the Stemcells in the environment and their associated CIDs.

Once the upload is complete, run `BOSH Stemcells` again. You should now see that the stemcell has a new CID.

$ bosh stemcells

+------------------------------------------+---------------+----------+-----------------------------------------+
| Name                                     | OS            | Version  | CID                                     |
+------------------------------------------+---------------+----------+-----------------------------------------+
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3232.17  | sc-2b99c89b-cad9-4f3a-9675-096e6c0b1402 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3232.21* | sc-53179aaf-9583-4670-b116-8bdfe3f372c5 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3233.3   | sc-xxxxxxxxxxxxxxx                      |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3233.8*  | sc-3878d9cb-e345-41bf-b5e2-53214efac0a0 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3262.2   | sc-15325687-589e-40f4-8826-5bc63a03ef1e |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3263.8*  | sc-2ef0597a-22fb-4888-88f8-3df4f03378dc |
+------------------------------------------+---------------+----------+-----------------------------------------+

Note the CID in the example above, one of the CIDs should match the CID listed in the error message from BOSH. Use this to determine the name, OS, and version of the missing Stemcell.

Once you have identified the Stemcell that is missing, download the appropriate Stemcell from Pivotal Networks and copy it to the Ops Manager VM.

From the Ops Manager VM, upload the Stemcell using the following command:

$ bosh upload stemcell bosh-stemcell-3263.8-vsphere-esxi-ubuntu-trusty-go_agent.tgz --fix
Acting as user 'director' on 'p-bosh-c23d4903cc1cb34e05eb'

Verifying stemcell...
File exists and readable                                     OK
Verifying tarball...
Read tarball                                                 OK
Manifest exists                                              OK
Stemcell image file                                          OK
Stemcell properties                                          OK

Stemcell info
-------------
Name:    bosh-vsphere-esxi-ubuntu-trusty-go_agent
Version: 3263.8

Uploading stemcell...

RSA 1024 bit CA certificates are loaded due to old openssl compatibility
bosh-stemcell:  96% |ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo    | 504.0MB  25.3MB/s ETA:  00:00:00
Director task 6122
  Started update stemcell
  Started update stemcell > Extracting stemcell archive. Done (00:00:05)
  Started update stemcell > Verifying stemcell manifest. Done (00:00:00)
  Started update stemcell > Checking if this stemcell already exists. Done (00:00:00)
  Started update stemcell > Uploading stemcell bosh-vsphere-esxi-ubuntu-trusty-go_agent/3263.8 to the cloud. Done (00:00:45)
  Started update stemcell > Save stemcell bosh-vsphere-esxi-ubuntu-trusty-go_agent/3263.8 (sc-fd9aed92-3919-4abb-bc6d-a36d40ff3d7c). Done (00:00:00)
     Done update stemcell (00:00:50)

Task 6122 done

Started		2016-12-25 18:47:22 UTC
Finished	2016-12-25 18:48:12 UTC
Duration	00:00:50
bosh-stemcell:  96% |ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo    | 505.1MB   7.0MB/s Time: 00:01:12

Stemcell uploaded and created.

Once the upload is complete, run `BOSH Stemcells` again. You should now see that the stemcell has a new CID.

$ bosh stemcells

+------------------------------------------+---------------+----------+-----------------------------------------+
| Name                                     | OS            | Version  | CID                                     |
+------------------------------------------+---------------+----------+-----------------------------------------+
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3232.17  | sc-2b99c89b-cad9-4f3a-9675-096e6c0b1402 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3232.21* | sc-8f32cd5e-70b4-41a9-bdbb-fb1cad99c2f8 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3233.3   | sc-586c54d1-c7f9-4c90-9f2b-cd6b0665c9f1 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3233.8*  | sc-3878d9cb-e345-41bf-b5e2-53214efac0a0 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3262.2   | sc-15325687-589e-40f4-8826-5bc63a03ef1e |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3263.8*  | sc-fd9aed92-3919-4abb-bc6d-a36d40ff3d7c |
+------------------------------------------+---------------+----------+-----------------------------------------+

Once done the error should be rectified, click on "Apply Changes" in the Ops Manager Web UI to continue deploying your changes.