SAS Viya 2024.09 Deployment RequestTimeout

[paul-blu]

Hey all,

I've tried to use the marketplace to deploy the newest version of SAS Viya and I'm running into an issue where the only error I get back is the RequestTimeout after 2 hours of the deployment being in progress. There are no other error messages.

I've tried it without whitelisted IPs, with whitelisted IPs, to no avail. I've tried to deploy it in Central US as that's the only region in US that currently has availability for the Standard_E16d_v4 in all 3 availability zones. Once again, the only error I'm getting is RequestTimeout after 2 hours. I have the correct quotas on my account as well, and I had this deployed about a month ago and it was working fine (I think it was the 2024.08 release)

Any tips would be great. Thanks

[paul-blu]

{

"code": "ResourceDeploymentFailure",

"target": "/subscriptions/redacted/resourceGroups/redacted/providers/Microsoft.Solutions/applications/redacted",

"message": "The resource provision operation did not complete within the allowed timeout period."

}

[JuanS_OCS]

Hi @paul-blu,

the number of reasons for this might be multiple. You could only get more information looking further in the logs.

First of all, I would try the deployment at a different day/time. Azure workloads can make big differences when you are running a deployment - remember, it is all shared resources in most cases.

Second, if that would not work, I would try a different version of SAS. Maybe try with 2024.08 (24.08.01), or even better, the really newest ones: Stable 2024.11, Stable 2024.10 or LTS 2024.09 (which I guess it might be the one you tried but on Stable version?).

If nothing of this works, the best is to reach out to Tech Support.

Ps. Please do note that Azure is changing some requirements this month too. The last things I heard is about the Kubernetes version and the SKU type for public IP addresses. I don't think this would affect a deployment so early, but it is surely to keep in mind for the coming few months. If you have a subscription, you might have received the emails from Microsoft already with the notification.

[paul-blu]

Hi, can you please explain how to use a different version on Azure? Like I said, the old 2024.07 version was working properly in eastus. Now the deployment just times out though, and I’m not sure where to look at the logs if you have any thoughts there I would appreciate it as well

[paul-blu]

Can you also share with me how to contact "Tech Support"? I've not been able to deploy SAS Viya for over 5 days, and our business uses it pretty heavily.

[cj_blake]

@paul-blu please see this post from Chris Hemedinger on the support resources available.

To help debug your deployment, it would be helpful if you could follow the instructions at this link and post them back to this thread. That should give us more information on the root cause of the deployment failure and timeout.

[paul-blu]

Hi Chris,

This is the "error message":

{

"status": "Failed",

"error": {

"code": "ResourceDeploymentFailure",

"target": "/subscriptions/redacted/resourceGroups/redacted/providers/Microsoft.Solutions/applications/redacted",

"message": "The resource provision operation did not complete within the allowed timeout period."

}

}

Like I said, we've been deployed in "eastus" before, and we have more than the required quotas. I was able to get the AZ access to "eastus" and I tried to redeploy this again in eastus but it is the same error. I've also tried "redeploying" the old version of the app (the 2024.07 deployment) from our deployment history, but it's also the same error.

I don't feel comfortable sharing account-specific identifiers on a public forum, so if there's any deeper debugging that can be done with Correlation IDs or Subscription IDs, I can share them privately.

[cj_blake]

@paul-blu I believe we have found the cause of the deployment failures after being able to replicate the behavior internally. We are working on a fix and will let you know as soon as that is released.

[paul-blu]

Hey CJ! Thank you so much, I will be waiting

[cj_blake]

@paul-blu this afternoon we have published a change to resolve the deployment issues that you were experiencing. Please try a new deployment from the Marketplace. If you can let me know the result of that deployment, that would be great.

Thanks!

[paul-blu]

Awesome! I ran the deployment and at least the URL is loading and I am able to access SAS Viya again.

Just so you know, the deployment still failed, and it's with the same error. I'm not sure if something actually failed or not, but I'll come back and keep you updated if something doesn't work as expected.

The only two things I can think of are:
1. I used the whitelisted IP setting
2. I used an existing resource group, and the region of that resource group is a different region than the actual deployment

[paul-blu]

Just looked at the managed resource group and found this error on the "-automation" step.

Maximum number of Accounts reached. If Deleted recently, please restore the same account

[cj_blake]

@paul-blu yes, we're aware of this and will be looking to resolve soon. That shouldn't affect the running of the system though. Those automations are convenience items for managing the deployment (stop, start) but those things can be done manually too.

[paul-blu]

Can you explain how to do these manually? I have no clue how to initiate a restart, start/stop, or change a whitelisted IP address. I cannot find it in your documentation either.