Provisioning a Managed Database

Behavior:

When provisioning a new Managed Database in MedStack Control, if you are running into a behavior where the Database server starts to spin up and shows up with a "Creating" state in your cluster and after 5 to 10 mins later it disappears from the cluster.

Cause:

The cause of this behavior is a provisioning error that is not communicated to the frontend. The root cause of this behavior is the value that is provided in the username field while creating a new database is rejected by the database. 

Solution:

To resolve this behavior and to successfully provision a database server, you need to make sure that the username of the managed database must only contain characters and numbers, however it cannot:

• Start with a number
• Start with "pg_"
• Contain hyphens
• Contain special characters ($,%,@,#,&,*, etc)
• Be any of:
  • azure_superuser
  • azure_pg_admin
  • admin
  • administrator
  • root
  • guest
  • public