Attention: This version of Event Streams has reached End of Support. For more information about supported versions, see the support matrix.

Cannot add schemas after installing earlier Event Streams version


If you install an earlier version of Event Streams on an IBM Cloud Private instance that already has an installation of Event Streams 2019.2.1, then the option to add schemas and schema versions becomes unavailable on the Event Streams 2019.2.1 installation.

The Add schema and Add schema version buttons are not available in the UI, and you cannot add schemas or schema versions by using the Event Streams CLI. For example, when running the cloudctl es schema-add command when logged in as a user with the correct permissions (Administrator or Operator roles), the following error is displayed:

cloudctl es schema-add /Users/jsmith/qp/schemas/ABC_schema_1.0.0.avsc
Event Streams API request failed:
Error response from server. Status code: 403. Forbidden

Unable to add version 1.0.0 of schema ABC_schema to the registry.


The IAM roles for schema registry authentication that are set up as part of the Event Streams 2019.2.1 installation are overwritten by the installation of an earlier version of Event Streams on the same IBM Cloud Private instance. This happens even when using a different namespace.

Resolving the problem

Restore the IAM roles for the schema registry authentication:

  1. Log in to your cluster as an administrator by using the IBM Cloud Private CLI:
    cloudctl login -a https://<Cluster Master Host>:<Cluster Master API Port>
    The master host and port for your cluster are set during the installation of IBM Cloud Private.
  2. List the ConfigMaps in the Event Streams 2019.2.1 installation:
    kubectl get configmaps -n <namespace>
  3. Find the role mappings ConfigMap from the list of ConfigMaps in the 2019.2.1 installation by looking for the ConfigMap with suffix role-mappings-cm.
  4. Download and save the configuration for the job stored in the ConfigMap:
    kubectl get configmap <RELEASE_NAME>-ibm-es-role-mappings-cm -o jsonpath='{.data.job}' > role-mappings-job.yml
  5. Run the following command to restore the security role mappings:
    kubectl create -f ./role-mappings-job.yml