Unable to push app with manifest.yml using a non-default stack

[amhuber]

Please fill out the issue checklist below and provide ALL the requested information.

• I reviewed open and closed github issues that may be related to my problem.
• I tried updating to the latest version of the CF CLI to see if it fixed my problem.
• I attempted to run the command with CF_TRACE=1 to help debug the issue.
• I am reporting a bug that others will be able to reproduce.
• If this is an issue for the v7 beta release, I've read through the official docs and the release notes.

Describe the bug and the command you saw an issue with
Using cf7 v7.0.2 I'm unable to push an app to the stack specified in the manifest. For example:

---
applications:
- name: aspxtest01
  stack: windows2012R2
  buildpacks:
  - hwc_buildpack
  instances: 1
  health-check-type: port

What happened
App failed to push.

cf push
Pushing app aspxtest01 to org test / space test as admin...
Applying manifest file C:\Development\aspxtest\manifest.yml...
For application 'aspxtest01': Buildpack "hwc_buildpack" must be an existing admin buildpack or a valid git URI 

If I override the stack on the command line, it does work:

cf push -s windows2012R2
Pushing app aspxtest01 to org test / space test as admin...
Applying manifest file C:\Development\aspxtest\manifest.yml...
Manifest applied
Packaging files to upload...
Uploading files...
 1.28 KiB / 1.28 KiB [=================================================================================================================================================] 100.00% 1s

Waiting for API to complete processing files...

Staging app and tracing logs...
   Downloading hwc_buildpack...
   Downloaded hwc_buildpack
   <snip>

Expected behavior
App should be deployed successfully, manifest works with cf v6.

To Reproduce

1. Create manifest per above.
2. cf push
3. See error

Provide more context

• API version: 3.87.0

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/174540704

The labels on this github issue will be updated when the story is started.

[heyjcollins]

Thanks for reporting this issue @amhuber. We're looking into this.
In the meantime and to help us out...
Could you please run cf buildpacks and include the output here for us?

[amhuber]

Sure, here you go:

Getting buildpacks as admin...

position   name                    stack           enabled   locked   filename
1          staticfile_buildpack    cflinuxfs3      true      false    staticfile_buildpack-cached-cflinuxfs3-v1.5.10.zip
2          java_buildpack          cflinuxfs3      true      false    java-buildpack-cflinuxfs3-offline-v4.32.1.zip
3          ruby_buildpack          cflinuxfs3      true      false    ruby_buildpack-cached-cflinuxfs3-v1.8.23.zip
4          dotnet_core_buildpack   cflinuxfs3      true      false    dotnet-core_buildpack-cached-cflinuxfs3-v2.3.14.zip
5          nodejs_buildpack        cflinuxfs3      true      false    nodejs_buildpack-cached-cflinuxfs3-v1.7.26.zip
6          go_buildpack            cflinuxfs3      true      false    go_buildpack-cached-cflinuxfs3-v1.9.17.zip
7          python_buildpack        cflinuxfs3      true      false    python_buildpack-cached-cflinuxfs3-v1.7.20.zip
8          php_buildpack           cflinuxfs3      true      false    php_buildpack-cached-cflinuxfs3-v4.4.20.zip
9          nginx_buildpack         cflinuxfs3      true      false    nginx_buildpack-cached-cflinuxfs3-v1.1.14.zip
10         binary_buildpack        cflinuxfs3      true      false    binary_buildpack-cached-cflinuxfs3-v1.0.36.zip
11         binary_buildpack        windows2012R2   true      false    binary_buildpack-cached-windows2012R2-v1.0.36.zip
12         hwc_buildpack           windows2012R2   true      false    hwc_buildpack-cached-windows2012R2-v3.1.15.zip

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/174612020

The labels on this github issue will be updated when the story is started.

[JenGoldstrich]

@tstannard and I discovered this issue is actually in the cf CLI code base, we have submitted a PR to fix this cloudfoundry/cli#2148 which should go out in the next cf CLI release.

Closing this now, please feel free to follow up further if you do not see this get resolved, thanks!

Jenna & Teal

[amhuber]

Thanks for following up on this, I'll monitor the CLI issue.