Long value for Zookeeper and Kafka persistent volume name field causes error

[EmmaHumber]

Issue Description

The following event is seen after install:

I0201 09:50:05.715206 1 event.go:221] Event(v1.ObjectReference{Kind:"StatefulSet", Namespace:"event-streams", Name:"evtstr-ibm-es-zookeeper-sts", UID:"800de1d1-2587-11e9-9317-0a0c9eb925fe", APIVersion:"apps/v1", ResourceVersion:"15048940", FieldPath:""}): type: 'Warning' reason: 'FailedCreate' create Pod evtstrbai-ibm-es-zookeeper-sts-0 in StatefulSet evtstrbai-ibm-es-zookeeper-sts failed error: Pod "evtstr-ibm-es-zookeeper-sts-0" is invalid: spec.containers[0].volumeMounts[0].name: Not found: "zookeeper-vol-pv"

The value supplied for the Zookeeper persistent volume name during install was too long resulting in an internal mapping of the name to fail.

This issue can also be seen with the Kafka persistent volume name.

Issue Resolution

The internal value sused for both the Zookeeper and Kafka persistent volume claim names are now all now shortened to matching values, and so the mapping no longer fails.

Workaround

Reduce the length of the name of the Zookeeper persistent volume name.

Fix details

IBM Internal issue number - 2449
Fix target - 2019.1.1