Deployment with -PrivateACR about ipam HOT 11 CLOSED

@DCMattyG thank you.

I have run a few tests and can confirm that I have a working solution with the -PrivateACR switch set.

I do not know what my cloned space had in it that prevented it from working as I could see all your latest code changes.

from ipam.

Hi @Garyforsman, thanks so much for reaching out!

Couple of questions...

1. Have you made sure that you've followed all of the prerequisites as shown in the docs here?

https://azure.github.io/ipam/#/deployment/README?id=prerequisites

2. I'm assuming you were doing a Full deployment, did you add any other flags besides "-PrivateACR"?

3. During the deployment, did you see any warnings/error messages?

From the above, it appears that NGINX cannot find the ipam-ui container running, which seems to me like something potentially failed in the docker build/push phase of the deployment script.

Please check the above, and if you're still having issues, I'm always happy to schedule a 1:1 session to help you out!

from ipam.

Hey @DCMattyG, thank you for the reply...much appreciated.

1. I have followed the prerequisites as documented in that link, I should also add that I am able to get a working deployment if I do and full deployment and do not use -PrivateACR
2. Correct, I am doing a full deployment with -PrivateACR
3. There are no errors noted during deployment

I will deploy again with the -PrivateACR flag on now and see if there are any errors noted. Will ping back here

from ipam.

@DCMattyG - It deploys with the below output (I have also attached the Docker log file)
WARNING: Selected Microsoft Graph profile 'v1.0' does not exist for module 'Microsoft.Graph.Financials'. No cmdlets were loaded.
WARNING: Selected Microsoft Graph profile 'v1.0' does not exist for module 'Microsoft.Graph.ManagedTenants'. No cmdlets were loaded.
WARNING: Selected Microsoft Graph profile 'v1.0' does not exist for module 'Microsoft.Graph.WindowsUpdates'. No cmdlets were loaded.

NOTE: IPAM Deployment Type: Full
INFO: PrivateACR flag set, verifying minimum Azure CLI version
INFO: PrivateACR flag set, verifying Azure PowerShell and Azure CLI contexts match
INFO: Fetching Tenant ID from Azure PowerShell SDK
INFO: Fetching Azure Cloud type from Azure PowerShell SDK
INFO: Validating Azure Region selected for deployment
INFO: Azure Region validated successfully
INFO: Creating Azure IPAM UI Application
INFO: Creating Azure IPAM Engine Application
INFO: Updating Azure IPAM Engine API Endpoint
INFO: Updating Azure IPAM UI Application Resource Access
INFO: Creating Azure IPAM UI Service Principal
INFO: Creating Azure IPAM Engine Service Principal
INFO: Creating Azure IPAM Engine Secret
INFO: Azure IPAM Engine & UI Applications/Service Principals created successfully
INFO: Logging in to Microsoft Graph
INFO: Granting admin consent for Microsoft Graph API permissions assigned to IPAM UI application
INFO: Admin consent for Microsoft Graph API permissions granted successfully
INFO: Granting admin consent to the IPAM UI application for exposed API from the IPAM Engine application
INFO: Admin consent for IPAM Engine exposed API granted successfully
INFO: Granting admin consent for Azure Service Management API permissions assigned to IPAM Engine application
INFO: Admin consent for Azure Service Management API permissions granted successfully
INFO: Deploying IPAM bicep templates
INFO: IPAM bicep templates deployed successfully
INFO: Updating UI Application with SPA configuration
INFO: UI Application SPA configuration update complete
INFO: Building and pushing container images to Azure Container Registry
INFO: Building Engine container (Debian)...
INFO: Engine container image build and push completed successfully
INFO: Building UI container (Debian)...
INFO: UI container image build and push completed successfully
INFO: Restarting App Service
INFO: Azure IPAM Solution deployed successfully
2022_10_27_ln0sdlwk0006L5_docker.log

from ipam.

Thanks for the output from the deploy script @Garyforsman!

It looks like you might want to verify the version of the Graph module you have installed as you shouldn't be seeing those warnings...

In looking at the logs you shared, it seems the containers weren't built correctly. Did you clone the entire repository with "git clone" and then run the deployment script from it's location in the /deploy folder? The init scripts are missing so it seems like the relative imports are missing/relocated?

The proper process is:

1. git clone https://github.com/Azure/ipam.git
2. cd ipam
3. cd deploy
4. .\deploy.ps1

Obviously the above instructions are for Windows, but hopefully you get the idea if you're running Linux/Mac.

from ipam.

@DCMattyG, I too am getting the same issue when using -PrivateACR

I've recently been looking at IPAM solutions and this one seems the best fit but I am looking to extend your argquery.py file to include filtering based on Azure Tags.

When using -PrivateACR, everything deploys but the UI doesnt work, and investigations also point to the init.sh files being missing.

Have tried Full and TemplateOnly deployments but neither work.

I also get the Microsoft.Graph warnings so have tried 1.15.x and 1.9.6.
I have also tried executing the ps1 script from within VSCode and from PowerShell terminal.

Any advice welcome as I'm actively trying to get this working.

Thanks,
Dan.

from ipam.

Hi @satsuk81, I have a branch with the fixes for this which will be merged today. For now, you can use the "nginx-ubi8" branch to deploy and the -PrivateACR flag should indeed work.

Please test and let me know if you run into any issues. Thanks so much!

Link: https://github.com/Azure/ipam/tree/nginx-ubi8

from ipam.

Fixes have been pushed, please let me know if you have any further issues on this topic!

from ipam.

@DCMattyG, unfortunately issue still remains. I tested yesterday with your branch and today on main.

log.zip

from ipam.

Hi @satsuk81, it appears you may still be using older code as the error present in the logs was something that I patched in the latest update. Can you please try deleting the cloned folder on your local machine, re-cloning from GitHub, and trying once more?

If that still doesn't work, drop me an email at [email protected] for some more 1:1 troubleshooting we can try.

Thanks!

from ipam.

That's wonderful news @satsuk81!

The issue I had patched (just so you know) was that the BASH scripts for the container startups were getting pushed up to GitHub with CRLF line endings instead of LF. I fixed this with a .gitattributes file, but it seems that despite that, when you did a "git pull", the line endings that you had locally already didn't properly switch back to LF from CRLF, causing issue when they were executed in the Linux containers.

So glad everything is working now!

from ipam.