search

Azure / azure-saas

The Azure SaaS Development Kit (ASDK) provides a reference architecture, deployable reference implementation and tools to help developers, startups, ISVs and Enterprises deliver their applications as a SaaS service. A platform for platform creators.
https://aka.ms/azuresaasdevkit
326 stars 239 forks source link

Run.sh doesn't run and gives below error. Can some one help ? #252

Open bhanupublicis opened 6 months ago

bhanupublicis commented 6 months ago

./run.sh
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

Welcome

Welcome to the Azure SaaS Dev Kit - Azure B2C Identity Provider deployment script.

Preparing

Working in directory /asdk/src/Saas.Identity/Saas.IdentityProvider/deployment.

Sudo

Please log in with sudo to run this script. You are logged in with sudo.

Checking prerequisites

Checking prerequisites...

Checking OS

Supported operating system: linux

Checking Repo forked

Forked repository true: git@github.com:bhanupublicis/azure-saas.git

Checking bash version

Pass: '5.1.16(1)-release > 5.0.0'

Checking az cli version

Pass: '2.55.0 > 2.46.0'

Checking jq version

Pass: '1.6 > 1.5'

Configation Settings

Initializing Configuration

Backup Configuration

Backing up existing configuration file to: /asdk/src/Saas.Identity/Saas.IdentityProvider/deployment/log/2023-12-12--16-41-02/config.begin.json Configuration settings: /asdk/src/Saas.Identity/Saas.IdentityProvider/deployment/config/config.json.

Postfix

Using existing postfix to continue or patch existing deployment: xlb8

Configuration Validation

Validating Initial Configuration Settings... All required initial configuration settings exist.

Login to Azure

Log into you Azure tenant Setting account subscription to ff09016f-c122-***.

You are logged in to tenant: d52c9ea1-7c21-***.

Critical error

Initilization failed cp: cannot stat '/asdk/src/Saas.Identity/Saas.IdentityProvider/deployment/config/certificate-policy.json': No such file or directory

Configuration Validation

Validating Initial Configuration Settings...

All required initial configuration settings exist.

Login to Azure

Log into you Azure tenant Setting account subscription to ff09016f-c122-***.

You are logged in to tenant: d52c9ea1-7c21-***

Critical error

Initilization failed cp: cannot stat '/asdk/src/Saas.Identity/Saas.IdentityProvider/deployment/config/certificate-policy.json': No such file or directory

Configuration Validation

Validating Initial Configuration Settings... All required initial configuration settings exist.

Cleaning up

Starting cleaning up...

Deleting locally stored service principal credentials. Deleting service principal credentials using user 'null' No known service principal to delete. Service principal credentials have been removed locally and in Azure AD. User context for null have been deleted. User context for null have been deleted. Clean up has completed.

Backup to Azure Blob Storage

Backing up logs in '/asdk/src/Saas.Identity/Saas.IdentityProvider/deployment/log/2023-12-12--16-41-02' to Azure Blob Storage 'null/null'. ERROR: Operation returned an invalid status 'Server failed to authenticate the request. Please refer to the information in the www-authenticate header.' ErrorCode:InvalidAuthenticationInfo

Deployment script completion

Identity Foundation deployed with errors. Sometimes this is due to an error happening with the Azure Resource Manager. Try running the script once more to see if it continues past the point of failure. Please review the log file for more details: /asdk/src/Saas.Identity/Saas.IdentityProvider/deployment/log/2023-12-12--16-41-02

1iveowl commented 6 months ago

Looks like you are trying to run the script from an ARM device. Correct?

bhanupublicis commented 6 months ago

Yes. im running from a Mac m1 chip arm device

1iveowl commented 6 months ago

We're testing with Apple Silicon. Will let you know if we can reproduce. Let us know if you have more observations. For instance, what was the result the first time you ran (./run.sh) the script? Did you get the same error message or a different one? You need to look at the log to see this.

1iveowl commented 6 months ago

Was able to reproduce the issue on Apple Silicon.

This seems to be the issue (and workaround): https://github.com/dotnet/runtime/issues/94909#issuecomment-1816543071

Will be updating the script with the workaround.

1iveowl commented 6 months ago

This should now have been addressed with #253.

Can you confirm if things are working for you now, @bhanupublicis?

Thank you