Pivotal Knowledge Base

Follow

Elastic Runtime deployment exits at step “+ cf set-env notifications SMTP_PASS” of “Notifications With UI” errand

Environment

Pivotal Cloud Foundry® 1.4.x

Symptom

This can be replicated when it matches both conditions as below:

  • "Notifications With UI" errand is turned on.
  • "SMTP Server Credentials" is left blank at SMTP Config page.
  • "SMTP Authentication Mechanism" is set to "none".

Deploy Elastic Runtime under above conditions, “Notifications With UI” errand exits with following error logs.

[stderr]
+ export PATH=/var/vcap/packages/cf_cli/bin:/var/vcap/packages/jq/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ PATH=/var/vcap/packages/cf_cli/bin:/var/vcap/packages/jq/bin:/usr/sbin:/usr/bin:/sbin:/bin
...
+ cf set-env notifications SMTP_AUTH_MECHANISM none
+ cf set-env notifications SMTP_CRAMMD5_SECRET ''
+ cf set-env notifications SMTP_HOST xxx.xxx.xxx.xxx
+ cf set-env notifications SMTP_PASS
{"type": "step_finished", "id": "errands.running.cf-baab9789d4e80ef8b82f.notifications"}
Exited with 1.

Cause
That operation fails because the Username/Password fields of "SMTP Server Credentials" are blank, so there are an incorrect number of arguments to command 'cf set-env'. The errand should be escaping those values with quotes, or simply skip the command when "SMTP Authentication Mechanism" is configured as "none".

Resolution

It is a known issue in Pivotal Cloud Foundry v1.4, the fix is planned to available in Pivotal Cloud Foundry v1.5 release.

As a temporary workaround for Pivotal Cloud Foundry v1.4, giving dummy Username/Password to "SMTP Server Credentials” helps to pass through 'cf set-env' command. There are no special side effect because the authentication passed to SMTP host will simply be ignored.

Comments

Powered by Zendesk