Chapter 5. Fixed issues
The following sections list the issues fixed in AMQ Streams 1.5.1 and 1.5.
5.1. Fixed issues for AMQ Streams 1.5.1
The AMQ Streams 1.5.1 patch release is now available. This micro release updates the Operator Metadata that is used to install AMQ Streams 1.5.0 from the OpenShift OperatorHub user interface. The AMQ Streams product images have not changed and remain at version 1.5.0.
Red Hat recommends that you upgrade to AMQ Streams 1.5.1 if you are using OpenShift Container Platform 4.5.
For additional details about the issues resolved in AMQ Streams 1.5.1, see AMQ Streams 1.5.x Resolved Issues.
5.2. Fixed issues for AMQ Streams 1.5
| Issue Number | Description |
|---|---|
|
Refactor | |
| Fix to generate new cluster or client secret/key when CA key deleted | |
| StorageDiff should handle scaling nodes up and down | |
| Exponential backoff in KafkaRoller sometimes takes 20+ minutes | |
| Improve the logging in KafkaRoller class | |
| KafkaConnectS2I doesn’t do rolling update after resources edit | |
| Automate ZooKeeper scaling | |
| Propagate all labels from template | |
| When KafkaConnect is scaled to 0 the reconciliation always timeouts | |
| Increase Cluster Operator memory limits from install YAMLs | |
| The CR of a topic returns the wrong status after decreasing partitions | |
|
The CR of a topic returns the wrong status after changing the value of | |
| Kafka Entity Operator has plain-text passwords in logs | |
| KafkaRoller blocks rolling update when topic with RF=1 and MIN-ISR=2 exists | |
| Cluster Operator fails to start on OCP | |
| Fix parsing of forbidden configuration options and their exceptions | |
| Fix the namespaces in RBAC files for installing the Cluster Operator to watch all namespaces | |
| Kafka cluster is ending up with duplicate kafkaTopic after upgrade from 1.3 to 1.4 |