SSLError: HTTPSConnectionPool when registering ML model on Azure

user_10382230 0
Viewed 855

Please I have my Databricks instance in a VNET. I’m trying to deploy my Machine learning model using the Azure ML workspace on Azure Container Instance (ACI).

I’m able to create an ML workspace. I get an SSLERROR when I try to register the Model using Model.register().

Using this code -

from azureml.core import Workspace
from azureml.core.model import Model
import azureml.core
from azureml.core.workspace import Workspace
from azureml.core.model import Model

from azureml.core import Workspace
   ws = Workspace.create(name='myworkspace',
               subscription_id='<azure-subscription-id>',
               resource_group='myresourcegroup',
               location='eastus'
               )

model_reg = Model.register(model_path = “./model_dir”,
                       model_name = "ModelX",
                      workspace = ws)

Find below the error when I try to deploy my model.

  SSL Error:

SSLError: HTTPSConnectionPool(host='eastus.experiments.azureml.net', port=443): Max retries exceeded with url: /discovery (Caused by SSLError(SSLError("bad handshake: SysCallError(104, 'ECONNRESET')")))
 

Please note only the Azure Databricks is in a VNET on Azure. How do I resolve it and deploy my model as a webservice on ACI.

Thank you.

azure-machine-learning-workbench azure-machine-learning-service azure-databricks azure ssl-certificate
1 Answers

EDIT: Here is some guidance I found on how to use Azure ML service with an Azure DataBricks cluster that lives inside of a virtual network:

To use Azure Databricks in a virtual network with your workspace, the following requirements must be met:

  • The virtual network must be in the same subscription and region as the Azure Machine Learning workspace.
  • If the Azure Storage Account(s) for the workspace are also secured in a virtual network, they must be in the same virtual network as the Azure Databricks cluster.
  • In addition to the databricks-private and databricks-public subnets used by Azure Databricks, the default subnet created for the virtual network is also required.

For specific information on using Azure Databricks with a virtual network, see Deploy Azure Databricks in your Azure Virtual Network.

Still could be a bug -- I see you've reported the error which the product team can take a look at. Meantime, Have you tried debugging locally yet? This guide does a good job of running through common failure modes.

user_38426100
Related