search

Azure / azure-remote-rendering

SDK and samples for Azure Remote Rendering
MIT License
106 stars 38 forks source link

ARR Showcase App - Failed to load model #44

Closed selinkampa closed 3 years ago

selinkampa commented 3 years ago

Hi,

Model names are listed correctly, and session is connecting without issues. The issue started happening since 2-3 weeks. Before we were able to load models from blob container without issues. Models are converted using ARRT, there in ARRT it is loading and rendering fine.

As I was using the release of Showcase app from some months ago, I thought maybe building it again might help, I pulled the latest release and took build, but no luck and still the same error.

I also have given storage account access to remote rendering account, following this documentation https://docs.microsoft.com/en-us/azure/remote-rendering/how-tos/create-an-account#link-storage-accounts: RR rr2

Thanks in advance.

ChristopherManthei commented 3 years ago

Hi @selinkampa,

thank you for the report. The reason ARRT works and Showcase not is most likely because ARRT uses LoadModelFromSasAsync and Showcase uses LoadModelAsync. So there is probably a problem with the storage account linkage. We are looking into the issue right now and will get back to you as soon as we can.

Cheers, Christopher

ChristopherManthei commented 3 years ago

It looks like the ARR account was moved to another subscription. In that case, the problem can probably be fixed by turning the system assigned managed identity off and on again: troubleshoot-portal-identity You might need to re-link your storage account with your arr account after doing this.

jeofyoung commented 3 years ago

Just wanted to add some info in addition to what @ChristopherManthei already covered:

Managed identities do not get updated when a subscription is transferred to another directory. As a result, any existing system-assigned or user-assigned managed identities will be broken. After the transfer, you can re-enable any system-assigned managed identities.

The same note applies even if only resources were moved to a subscription in a different tenant instead of the whole subscription.

Managed identities do not currently support cross-directory scenarios.

To summarize:

Apologies for the inconvenience.

selinkampa commented 3 years ago

Dear @ChristopherManthei and @jeofyoung, thank you so much for the support.

It was indeed about the migration of the tenant, there must be something going wrong during that.

First I tried toggling "System assigned", which did remove the "undefined identity" and the name of the remote rendering account was shown in the assigned roles list again. But that didn't fix the issue, and I still couldn't load models.

In the separate thread, I received one more comment additional to what you said, which is to open a new remote rendering account if toggling wouldn't help. Once I opened a second remote rendering account in the new tenant and linked it with the existent blob storage, and took another Unity build with the new keys, it worked! We can render remotely again :)

Great work and support! Thanks once more.

jeofyoung commented 3 years ago

Hi @selinkampa,

Thank you very much for reporting your results after re-creating the identity. It seems that something we enabled recently is causing an issue that prevented the newly created identity for your old account from getting registered which we will resolve. Thanks for helping us uncover this!

jeofyoung commented 3 years ago

The issue preventing a re-created identity from being registered in the system has been resolved.