Deploying a Function App with --deployment-container-image-name can result in a Function App that will not start.

[FinVamp1]

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
The validation for --deployment-container-image-name can result in a Function App that will start as it sets the LinuxFxVersion correctly.

The linuxFxVersion should be /imagename:tags>

The validation logic at

azure-cli/src/azure-cli/azure/cli/command_modules/appservice/custom.py

Line 1227 in 6c1b085

def _format_fx_version(custom_image_name, container_config_type=None):

doesn't seem to check this for the Functions scenarios.

To Reproduce

1. Install the newest Az Cli.
2. Create a Storage Account, Resource Group and Managed Identity.
3. Run this command.

az functionapp create --name --resource-group \
--storage-account \
--plan <planName \
--functions-version 3 \
--runtime python \
--os-type Linux \
--deployment-container-image-name imageName:tags \
--assign-identity

4. You will see a Function App that is created but has no Functions and returns a Server error.
5. The internal logs show the docker pull is failing/
6. Updating the Linux Fx Version to DockerId/imagename:tags works.

Expected behavior

1. That the Function App starts.

Environment summary
Reproduced using the Azure Cloud Shell.

Additional context
https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-function-linux-custom-image
https://docs.microsoft.com/en-us/azure/app-service/configure-custom-container?pivots=container-linux#change-the-docker-image-of-a-custom-container

Thank you for your feedback. This has been routed to the support team for assistance.

Thank you for your feedback. This has been routed to the support team for assistance.

[yonzhan]

route to CXP team to help with

[SatishBoddu-MSFT]

Hello @FinVamp1 Thanks for the context!

As we do have an internal Incident ticket created on this issue, i am routing this to the service team asap.

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ahmedelnably, @fabiocav.

Issue Details

---

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
The validation for --deployment-container-image-name can result in a Function App that will start as it sets the LinuxFxVersion correctly.

The linuxFxVersion should be /imagename:tags>

The validation logic at

azure-cli/src/azure-cli/azure/cli/command_modules/appservice/custom.py

Line 1227 in 6c1b085

def _format_fx_version(custom_image_name, container_config_type=None):

doesn't seem to check this for the Functions scenarios.

To Reproduce

1. Install the newest Az Cli.
2. Create a Storage Account, Resource Group and Managed Identity.
3. Run this command.

az functionapp create --name --resource-group \
--storage-account \
--plan <planName \
--functions-version 3 \
--runtime python \
--os-type Linux \
--deployment-container-image-name imageName:tags \
--assign-identity

4. You will see a Function App that is created but has no Functions and returns a Server error.
5. The internal logs show the docker pull is failing/
6. Updating the Linux Fx Version to DockerId/imagename:tags works.

Expected behavior

1. That the Function App starts.

Environment summary
Reproduced using the Azure Cloud Shell.

Additional context
https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-function-linux-custom-image
https://docs.microsoft.com/en-us/azure/app-service/configure-custom-container?pivots=container-linux#change-the-docker-image-of-a-custom-container

Author:	FinVamp1
Assignees:	-
Labels:	Service Attention, Functions
Milestone:	-

[pragnagopa]

We do not expect customers to set LinuxFxVersion with blessed image - combination of FUNCTIONS_EXTENSION_VERSION and linuxFxVersion - runtime|version - should work - for example - For V3 python 3.7 app

FUNCTIONS_EXTENSION_VERSION should be set to ~3
linuxFxVersion should be set to python|3.7