Skip to main content
print this page

Deletion of existing stream while creating new stream with the same name

· 2 min read
Fix Available

When attempting to create a new stream with a name that already exists within the system, the existing stream is erroneously deleted from the backend and results in an inability for the user to use the stream with a ‘ParameterNotFound’ error.

Affected Versions: 2.3 2.2

Fix Version: 2.4

Root cause(s)

The issue arises due to the system incorrectly interpreting existing stream resources as newly created ones during the process of creating a stream with a duplicate name. This misinterpretation leads to the cleanup of the existing resources when the creation fails.

Impact

This behavior results in the loss of data and disrupts the expected functionality.

Mitigation

Workaround

Refrain from creating streams using names that already exist. If necessary, create new streams only subsequent to deleting the previously existing stream.

Fix available

Fix is available in Amorphic v2.4. Please upgrade to the latest version to resolve this issue.

Timeline

  • 2023-11-21: Bug reported/identified (CLOUD-4121)
  • 2023-11-21: Bug triaged
  • 2023-11-21: Bug fixed
  • 2023-11-21: Testing completed and fix is available