Skip to content

Is there currently a bug with creating clones of clusters in DocumentDB?

0

Following the same steps I have previously done to create a clone for one of my clusters, I was greeted with a blank white page instead of the options for creating my clone. Looking at the browser console, I have the following error - 291.js:2 TypeError: n.some is not a function Letting the page sit for a little while does not help either. To repro, I just selected the cluster I wanted to clone, clicked actions, then create clone.

asked a year ago110 views
1 Answer
0

Based on the information provided in the official Amazon DocumentDB documentation, there is no mention of a known bug related to creating clones of clusters in DocumentDB. The cloning feature is described as a functional capability of the service.

However, the issue you're experiencing with a blank white page and the JavaScript error you've encountered in the browser console is not a documented behavior or known limitation of the Amazon DocumentDB cloning process. This appears to be a user interface or web console issue rather than a problem with the underlying DocumentDB cloning functionality.

The error message you're seeing (TypeError: n.some is not a function) suggests there might be a JavaScript-related problem in the AWS Management Console interface. This could be due to various factors such as browser compatibility issues, temporary glitches in the AWS console, or potentially a recent change that introduced an unintended bug in the user interface.

If you're encountering this issue consistently, it would be advisable to try the following troubleshooting steps:

  1. Clear your browser cache and cookies, then try again.
  2. Use a different web browser to access the AWS Management Console.
  3. If possible, attempt to create the clone using the AWS CLI instead of the console.
  4. Contact AWS support to report the issue, as they would be best positioned to address any recent changes or bugs in the console interface.

It's important to note that while the web interface might be experiencing issues, the underlying DocumentDB cloning functionality should still be operational. If the problem persists, using the AWS CLI or AWS SDKs to create the clone could be a viable alternative until the console issue is resolved.
Sources
Cloning a volume for an Amazon DocumentDB cluster - Amazon DocumentDB
CreateDBCluster - Amazon DocumentDB

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.