Unable to run loadSampleData.sh script on hybrid systems

An error is returned when running the loadSampleData.sh script on a hybrid environment on an SSL ObjectServer. On hybrid systems in general, the replaying of historic events to an SSL enabled ObjectServer is not supported . Attempts to do so result in a write: broken pipe error.

Problem

An error is returned when running the loadSampleData.sh script on a hybrid environment on an SSL ObjectServer.

Cause

The ea-events-tooling used to load sample data into a system does not support SSL.

Resolution

  1. Run the example command that you find after running oc get noihybrid, to get a template called loadsampleData.yaml
    Note: You need to have at least one port exposed on the object server that does not use SSL.
  2. Make the following changes to load the sample data into the remote object server:
    • Remove the volumes block, where $RELEASE_NAME, is the name of your release:
            volumes:
            - name: ca
              secret:
                secretName: $RELEASE_NAME-omni-certificate-secret
                items:
                - key: ROOTCA
                  path: rootca
    • Remove the following ca volume mount section from the container specifications at the installdemoeventsfortraining:
              volumeMounts:
              - name: ca
                mountPath: /ca
                readOnly: true
      
    • Remove the following parameters at the container installdemoeventsfortraining. $RELEASE_NAME corresponds to your release name.
              - name: NOIOMNIBUS_OS_TRUSTSTORE_PASSWORD
                valueFrom:
                  secretKeyRef:
                    name: $RELEASE_NAME-omni-certificate-secret
                    key: PASSWORD
                    optional: false
              - name: NOIOMNIBUS_OS_TRUSTSTORE_PATH
                value: "/ca/omnibusTrustStore"
              - name: NOIOMNIBUS_OS_SSL_PROTOCOL
                value: "TLSv1.2"
    • Modify the object server port number from:
            - name: $RELEASE_NAME_OBJSERV_AGG_PRIMARY_SERVICE_PORT
                value: "secure port number"
      To a non SSL port number, for example, 9100:
              - name: $RELEASE_NAME_OBJSERV_AGG_PRIMARY_SERVICE_PORT
                value: "9100"
    You can find the non SSL port number by referring to the omni.dat file in your remote system. Note that if there is no none-ssl port number configured you cannot use these utilities.
    Draft comment: posnerke@uk.ibm.com
    Issues 1937 and 6708