[REDIS] `az redis create` doesn't wait for provisioning to complete
See original GitHub issueWhen running az redis create
the command returns while the provisioning state is still Creating
. Unless --no-wait
is applied, I’d expect the command to return upon completing provisioning.
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Configure caches in Azure Cache for Redis using Ansible
Learn how to use Ansible to create, scale, reboot, and add a firewall rule to Azure Cache ... name: Wait for Redis provisioning...
Read more >Manage Azure Cache for Redis instance
Wait till the Azure Cache for Redis instance provisioning_state is Succeeded. It takes several minutes for Azure Cache for Redis to be provisioned...
Read more >Minimizing downtime in ElastiCache for Redis with Multi-AZ
There is no need to create and provision a new primary node, because ElastiCache will handle this transparently. This failover and replica promotion...
Read more >AWS ElastiCache for Redis: How to Use the AWS Redis Service
Before you can begin using the Amazon ElastiCache Redis service, you'll need to set up your AWS environment. Here's a quick walkthrough on...
Read more >cloudposse/elasticache-redis/aws - Terraform Registry
Terraform module to provision an ElastiCache Redis Cluster ... IMPORTANT: We do not pin modules to versions in our examples because of the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Redis spec of 2017 and spec of 2018 marked this operation as long running operation, but the actual behavior is not as expected. It’s a history mistake.
Considering that current user did’t report or vote similar problem and also redis is a frequently used service of Azure, correcting this behavior would break many user’s daily work which confusing them a lot and consuming them a lot of time to figure out.
So, it’s fine to close.
However, If there are new users report similar question like this, redis service should fix that we insist.
@MyronFanQiu @tjprescott What do you think?