REST API responds 202 but not succeeded

[KuniyoshiKamimura]

Describe the bug
Rest API call responds 202 but not succeeded.

To Reproduce
Steps to reproduce the behavior:

1. Do curl request as below.
2. The response code is 202.
3. No change has been made to AppService.
4. There's Exception in Application Insights.

Curl:

$ curl -X POST -i https://func-acme-bot-kjwk.azurewebsites.net/api/certificate -H "Content-Type: application/json" -H "x-functions-key: ***" -d '{"ResourceGroupName": "***", "AppName": "***", "SlotName": "production", "DnsNames": ["***"]}'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   132    0     0  100   132      0    135 --:--:-- --:--:-- --:--:--   135HTTP/1.1 202 Accepted
Cache-Control: no-store
Location: https://func-acme-bot-kjwk.azurewebsites.net/api/certificate/842b5e58f4b245b38740e1be95e527b7
Request-Context: appId=cid-v1:e2afb886-5995-48a9-9453-b6e06fecd866
Date: Sun, 27 Dec 2020 10:55:01 GMT
Content-Length: 0

Application Insights:

時間	19:52:21
期間	59 ms
送信コマンド	GET /subscriptions/c97f984d-81ff-428f-ac34-6bfe02837bb4/resourceGroups/ReviewPlatform/providers/Microsoft.Web/sites/ReviewPlatform-Prod
結果コード	403
LogLevel	Information
ProcessId	12928
HostInstanceId	5f42a361-f5b9-4f92-89d6-79362f0669de
https://management.azure.com/subscriptions/c97f984d-81ff-428f-ac34-6bfe02837bb4/resourceGroups/ReviewPlatform/providers/Microsoft.Web/sites/ReviewPlatform-Prod?api-version=2020-06-01

時間	19:52:22
例外の種類	Microsoft.Azure.WebJobs.Host.FunctionInvocationException
例外メッセージ	Exception while executing function: GetSite <--- Operation returned an invalid status code 'Forbidden'
LogLevel	Error
prop__executionDuration	2763
EventId	3
Microsoft.Azure.WebJobs.Host.FunctionInvocationException: Exception while executing function: GetSite
 ---> Microsoft.Azure.Management.WebSites.Models.DefaultErrorResponseException: Operation returned an invalid status code 'Forbidden'
   at Microsoft.Azure.Management.WebSites.WebAppsOperations.GetWithHttpMessagesAsync(String resourceGroupName, String name, Dictionary`2 customHeaders, CancellationToken cancellationToken)
   at Microsoft.Azure.Management.WebSites.WebAppsOperationsExtensions.GetAsync(IWebAppsOperations operations, String resourceGroupName, String name, CancellationToken cancellationToken)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionInvoker`2.InvokeAsync(Object instance, Object[] arguments) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionInvoker.cs:line 52
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.InvokeWithTimeoutAsync(IFunctionInvoker invoker, ParameterHelper parameterHelper, CancellationTokenSource timeoutTokenSource, CancellationTokenSource functionCancellationTokenSource, Boolean throwOnTimeout, TimeSpan timerInterval, IFunctionInstance instance) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:line 559
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.ExecuteWithWatchersAsync(IFunctionInstanceEx instance, ParameterHelper parameterHelper, ILogger logger, CancellationTokenSource functionCancellationTokenSource) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:line 505
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.ExecuteWithLoggingAsync(IFunctionInstanceEx instance, FunctionStartedMessage message, FunctionInstanceLogEntry instanceLogEntry, ParameterHelper parameterHelper, ILogger logger, CancellationToken cancellationToken) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:line 283
   --- End of inner exception stack trace ---
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.ExecuteWithLoggingAsync(IFunctionInstanceEx instance, FunctionStartedMessage message, FunctionInstanceLogEntry instanceLogEntry, ParameterHelper parameterHelper, ILogger logger, CancellationToken cancellationToken) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:line 330
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.TryExecuteAsync(IFunctionInstance functionInstance, CancellationToken cancellationToken) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:line 94

Environment (please complete the following information):

• App Service OS: Windows
• App Service Type: ASP.NET MVC
• Runtime Stack: .NET v4.8
• Certificate Type: naked

Additional context
There's no description about 202 in the document.
202 should be in the document or app should not responds 202.

[shibayan]

Since the certificate issuing API is an asynchronous process, it will return 202 and the actual status return URL will be returned in Location. Therefore, it is not a bug.

It seems that the RBAC settings are insufficient, so please read the README and review the settings.

[KuniyoshiKamimura]

This is my RBAC settings.

This is what I get.

Even if I grant more, I got same result.

Anything wrong?

[KuniyoshiKamimura]

Note that I have all resources in the same resource group.

[KuniyoshiKamimura]

I was trying to install certification via "Azure Let's Encrypt" extension and it also failed.
After I struggled for many times, I realized the reason.
I've applied IP address restriction for App Service and it prevented Let's Encrypt to access to my site.
I didn't noticed for long time because I can access to the site.

I haven't confirmed that the failure in this topic have the same reason but maybe it is.
It's OK for me to close the case now.
Thank you for your cooperation.