Part of buildpacks are missing when upgrading CF from v158 to v172

[xiangy...@emc.com]

We are upgrading our CF env from v158 to v172. But we found only part of buildpacks specified in v172 yaml file were installed in CC.

 

    default_buildpacks:
    - name: java_offline_buildpack
      package: buildpack_java_offline
    - name: ruby_buildpack
      package: buildpack_ruby
    - name: nodejs_buildpack
      package: buildpack_nodejs
    - name: go_buildpack
      package: buildpack_go

    install_buildpacks:
    - name: java_offline_buildpack
      package: buildpack_java_offline
    - name: ruby_buildpack
      package: buildpack_ruby
    - name: nodejs_buildpack
      package: buildpack_nodejs
    - name: go_buildpack
      package: buildpack_go

    system_buildpacks:
    - name: java_offline_buildpack
      package: buildpack_java_offline
    - name: ruby_buildpack
      package: buildpack_ruby
    - name: nodejs_buildpack
      package: buildpack_nodejs
    - name: go_buildpack
      package: buildpack_go

 

Getting buildpacks...

buildpack                position   enabled   locked   filename  
ruby_buildpack           2          true      false    buildpack_ruby_v46-245-g2fc4ad8.zip  
nodejs_buildpack         3          true      false    buildpack_nodejs_v8-177-g2b0a5cf.zip  
go_buildpack             4          true      false    buildpack_go_cf-v1-4-geeb56b9.zip

 

Obviously, the java_offline_buildpack was not installed. But after I ran "bosh recreate cc_hm 0" and "bosh restart cc_hm 0", all buildpack were there.

 

Getting buildpacks...

buildpack                position   enabled   locked   filename  
java_offline_buildpack   1          true      false    java-buildpack-offline-v2.1.2.zip  
ruby_buildpack           2          true      false    buildpack_ruby_v46-245-g2fc4ad8.zip  
nodejs_buildpack         3          true      false    buildpack_nodejs_v8-177-g2b0a5cf.zip  
go_buildpack             4          true      false    buildpack_go_cf-v1-4-geeb56b9.zip

 

I attached the yaml file we used. Would anybody tell me why the configuration didn't work at first, but worked when recreate the vm?

 

Thanks,

Maggie

[Michael Fraenkel]

There have been updates to how buildpacks are installed since v172.

There are a couple of log files you can look at to see if any error was reported.  The Jobs table may also have captured the failure.

[xiangy...@emc.com]

Hi, Michael

 

I installed buildpacks when deploying v172. I specified all buildpacks I want to installed in my yaml file.

 

Is there recommended way to install buildpack in v172?

 

Would you please tell me which specific log file I should check? How do I check jobs table?

 

Thanks a lot for your help!

 

Maggie

[Michael Fraenkel]

You will need to get on api_z1 and examine the logs there.  I can't say which one it will be in since it has changed since then.

As far as jobs are concerned, you can either look directly in CCDB for the delayed_job table.