Full output of while commands not shown

[anEXPer]

The full output of a no-op bosh-deploy looks like this:

+ bosh -n -d cf deploy /tmp/tmp.hACFvYqcy1
Using environment 'https://35.165.126.82:25555' as client 'admin'

Using deployment 'cf'

Release 'binary-buildpack/1.0.13' already exists.

Release 'capi/1.33.0' already exists.

Release 'cf-networking/1.2.0' already exists.

Release 'cf-smoke-tests/36' already exists.

Release 'cflinuxfs2/1.137.0' already exists.

Release 'consul/171' already exists.

Release 'diego/1.22.0' already exists.

Release 'dotnet-core-buildpack/1.0.21' already exists.

Release 'etcd/117' already exists.

Release 'garden-runc/1.9.0' already exists.

Release 'go-buildpack/1.8.5' already exists.

Release 'java-buildpack/3.18' already exists.

Release 'loggregator/91' already exists.

Release 'nats/21' already exists.

Release 'nodejs-buildpack/1.6.2' already exists.

Release 'php-buildpack/4.3.37' already exists.

Release 'python-buildpack/1.5.20' already exists.

Release 'routing/0.159.0' already exists.

Release 'ruby-buildpack/1.6.43' already exists.

Release 'staticfile-buildpack/1.4.10' already exists.

Release 'statsd-injector/1.0.28' already exists.

Release 'uaa/41' already exists.

Release 'garden-windows/0.5.0' already exists.

Release 'hwc-buildpack/2.3.4' already exists.

Release 'datadog-firehose-nozzle/59' already exists.

Task 17183

11:05:11 | Preparing deployment: Preparing deployment (00:00:02)
11:05:19 | Preparing package compilation: Finding packages to compile (00:00:00)

Started  Fri Jul 14 11:05:11 UTC 2017
Finished Fri Jul 14 11:05:19 UTC 2017
Duration 00:00:08

Task 17183 done

Succeeded

In a recent build using uptimer, the output looked like this:

[UPTIMER] 2017/07/25 06:38:49 Running command: `bosh -n deploy /tmp/tmp.NnQCYPJiiX -d cf`

06:38:54 | Preparing deployment: Preparing deployment (00:00:02)
06:39:02 | Preparing package compilation: Finding packages to compile (00:00:00)
[UPTIMER] 2017/07/25 06:39:03 

[UPTIMER] 2017/07/25 06:39:03 Finished running command

Clearly something is missing. Are we getting both standard error and standard out? Is something else going on?

[cf-gitbot]

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

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

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

[dsabeti]

@anEXPer, I just performed a no-op deploy, and redirected stdout and stderr to different files. The Release 'X' already exists. message was missing from both files.

I'm not too worried, since it looks like we're getting the output that we care about, but it's worth following up with @cppforlife to understand what's going on.

[dsabeti]

And then, by shear dumb luck, somebody asked about this in Slack. I'll co-opt this issue into a story to provide -tty to the bosh CLI.

[dsabeti]

This has been fixed in cf-deployment-concourse-tasks: https://github.com/cloudfoundry/cf-deployment-concourse-tasks/commit/6b7000942de5bc69b6370825f9cd57a9fcfa4ecd

Closing this issue.