Loading...

XML

Word

Printable

Release Note Text:

Hide
Previously, if you deployed a Custom Resource (CR) instance to create an Operator-based broker deployment, the Operator created a StatefulSet for the deployment, immediately removed the StatefulSet, and then created it one more time. As a result of this issue, the broker Pods created for the deployment started, immediately terminated, and then started again. This issue is now resolved.

Show
Previously, if you deployed a Custom Resource (CR) instance to create an Operator-based broker deployment, the Operator created a StatefulSet for the deployment, immediately removed the StatefulSet, and then created it one more time. As a result of this issue, the broker Pods created for the deployment started, immediately terminated, and then started again. This issue is now resolved.
Release Note Status:
Documented as Resolved Issue
Target Release:

AMQ 7.7.0.GA
Steps to Reproduce:

Hide

Create an ActiveMQArtemis custom resource instance watching closely in the gui on startup, depending on the speed of updates statefulset may appear, disappear and then reappear.

Show
Create an ActiveMQArtemis custom resource instance watching closely in the gui on startup, depending on the speed of updates statefulset may appear, disappear and then reappear.

At the moment when the user creates an ActiveMQArtemis custom resource instance the operator responds by what appears to be the following sequence:

This causes issues such as pods appearing to start and then immediately terminate among others. This may be related to this line of code

There are no Sub-Tasks for this issue.