Hi Dan

Check with the bosh cli options rgd the vms and status check.

On Wed, Mar 16, 2016 at 9:35 PM, Eric Malm <emalm(a)pivotal.io> wrote:

Hi, Dan,

It may be a regression in the CF CLI: in my check against one of the
Diego team environments, that stack field is consistently absent after the
initial push with CLI 6.16.1+924508c-2016-02-26, but
consistently present with 6.14.1+dc6adf6-2015-12-22 (the other version I
had at hand on my system).

Thanks,
Eric

On Wed, Mar 16, 2016 at 8:44 AM, Edward Mikuszewski <
emikuszewski(a)pivotal.io> wrote:

Great question, Dan. I'm curious to this as well - I just assumed it
took some time to report back the status.

On Wed, Mar 16, 2016 at 10:28 AM, Daniel Mikusa <dmikusa(a)pivotal.io>
wrote:

Quick question, when I push an app to CF I get this output at the
bottom after the app starts.

```
requested state: started
instances: 1/1
usage: 256M x 1 instances
urls: sinatra-test-dan.cfapps.io
last uploaded: Wed Mar 16 14:54:50 UTC 2016
stack: unknown
buildpack: https://github.com/cloudfoundry/ruby-buildpack#v1.6.5

state since cpu memory disk
details
#0 running 2016-03-16 10:55:12 AM 0.1% 21M of 256M 68.3M of 1G
```

Anyone know why the stack always reports "unknown"? If I run `cf app`
right after, it will report the stack properly. It only shows up this way
on the initial push.

Versions:
- cf version 6.16.1+924508c-2016-02-26
- cf v231
- diego 0.1454.0
- garden 0.333.0

Thanks,

Dan

--
Ed Mikuszewski *| * <http://www.pivotal.io> *|* Mobile: 646-628-2872
*| *Email: emikuszewski(a)pivotal.io