1-node MongoDB cluster temporarily goes into error state during initial provisioning

Description

User impact:

An incorrect cluster state misleads the user into thinking that there’s something wrong while the cluster is going through the “normal” initialization.

Steps to reproduce:

Create any 1-node MongoDB cluster.

Actual result:

Cluster status: no state -> Error -> Ready

Expected result:

Cluster status: no state -> Initializing -> Ready

Workaround (if one exists):

Environment:

Environment

None

Activity

Edith Erika Puclla Pareja 
December 30, 2024 at 11:42 AM

More details about similar issue with MongoDB:

Details

Assignee

Reporter

Affects versions

Priority

Created November 26, 2024 at 10:55 AM
Updated January 30, 2025 at 9:48 AM