topic Re: Models signature inaccessible in Unity Catalog in Data Governance

Models signature inaccessible in Unity Catalog

owlleg6 — Sun, 12 Nov 2023 10:49:34 GMT

I am using Unity Catalog to store my models. My Unity Catalog meta-store is hosted in an Azure Storage Account, which has public network access disabled. Access is restricted to certain IP ranges and private endpoint connections only.

Recently, my development team has noticed that the signatures of the models are inaccessible, although we can access every table, volume, etc., using the Private Endpoint connected to the Storage Account. Interestingly, if I open the Storage Account to the public network, the model signatures become accessible. Could you please explain why all folders within the Unity Catalog meta-store are accessible except for the 'models' folder?

Re: Models signature inaccessible in Unity Catalog

owlleg6 — Sun, 12 Nov 2023 20:55:09 GMT

This exception from mlflow when downloading artifact

Re: Models signature inaccessible in Unity Catalog

Rikard007 — Thu, 21 Dec 2023 21:23:50 GMT

We are facing the same issue. We can’t reconsider security setup since that is enforced by IT security. Does anyone have suggestions on how to resolve this issue so we can save and access the signatures from models stored in UC?

Re: Models signature inaccessible in Unity Catalog

owlleg6 — Tue, 02 Jan 2024 11:03:14 GMT

Hello, your moderators are deleting my previous replies, that's funny something is not working properly, i am trying to find out the solution but you are deleting the posts.
So, the issue is with a networking for sure, not with the permissions. Where can i raise a ticket? This is critical issue for my team, we have to disable public access to Storage Account.

Cheers

Re: Models signature inaccessible in Unity Catalog

lbdatauser — Fri, 12 Jan 2024 18:28:54 GMT

I have the same problem. It must be a permissions issue. In my case, it happens when the models are under a schema that was created without indicating a specific "MANAGED LOCATION". In those cases, I also have problems trying to load a model. When the models are under a schema created with a particular "MANAGED LOCATION" all works ok for me.

Re: Models signature inaccessible in Unity Catalog

owlleg6 — Wed, 28 Feb 2024 11:36:09 GMT

Fair point, what if i don't want to use External Locations for Schemas where models will be stored? Why default Metastore location does not allow accessing signatures.

Re: Models signature inaccessible in Unity Catalog

myroslava — Wed, 16 Oct 2024 11:58:34 GMT

Experiencing the same problem, when calling

model_version_uri = "models:/catalog_name.schema_name.model_name/version"

first_version = mlflow.pyfunc.load_model(model_version_uri)

mlflow.store.artifact.cloud_artifact_repo: Failed to complete request, possibly due to credential expiration. Refreshing credentials and trying again...

My schema has MANAGED LOCATION but still - same problem. Did anybody succeed in fixing this?

Re: Models signature inaccessible in Unity Catalog

myroslava — Fri, 18 Oct 2024 07:54:19 GMT

Got issue fixed:

The issue was with Private Endpoint: we had PE with dfs sub-resource only, but mlflow uses blob, so when I created PE with blob sub-resource - the issue was fixed. (also blob DNS zone and network link is needed)