@Leo, Sabato
I think this is because of a recent change in the SDK, release notes are mentioned
here
.
This change is causing an issue:
azureml-defaults
We are removing the dependency azureml-model-management-sdk==1.0.1b6.post1 from azureml-defaults.
An
issue
is also reported on a different github repo.
The workaround for now is to update your conda environment yaml file to include the package
azureml-model-management-sdk
under pip after
azureml-defaults
I hope this helps.
I also tried to roll back to the previous version of azureml-defaults (same environment that works for previous models) but it fails as well.
Maybe only changing the yaml file though Azure Store Explorer is not enough?
Final attempt with the modified yml below also gave the same problem.
It seams that modifying the yaml file in the outputs folder of the model I want to deploy has no effect as if dependencies are read from somewhere else.
Any idea?
azureml-train-automl-runtime==1.33.0
inference-schema
azureml-interpret==1.33.0
azureml-defaults==1.33.0
azure-ml-api-sdk
azureml-model-management-sdk
@romungi-MSFT
Also this scenario (modify the yml file using Storage Manager, upload it to the cloud and trigger the deploy from the Portal) fails.
However I got a different error this time:
Starting gunicorn 20.1.0
Listening at:
http://127.0.0.1:31311
(11)
Using worker: sync
worker timeout is set to 300
Booting worker with pid: 38
SPARK_HOME not set. Skipping PySpark Initialization.
Generating new fontManager, this may take some time...
Hello
I also got in to this issue 3 days back when I tried to deploy a pytorch based recommender model with a newer variation. I tried with both the recommended solution - explicitly installing either the library
azure-ml-api-sdk
. or
azureml-model-management-sdk
Both landed on this new error
message": "Error in entry script, AttributeError: Can't get attribute 'new_block' on <module 'pandas.core.internals.blocks' from '/azureml-envs/azureml_a9071edb452f2dedb0ab60b9e2450ad3/lib/python
Somewhere I found that Pandas 1.3 is causing this error and 1.2 would solve it- I tried with Pandas 1.2 / 0.25 also but the "Cant get Attribute "new block" stays --
I had to reschedule a planned demo as I never thought I would get this problem for a very similar model that is running in production.
Any help is much appreciated -
Thanks
Update
The
pandas 1.2 library
is working for this issue- Originally I was using it as a reference in the YML file during deployment - But I tried changing it in my environment and ran all the scripts including train and validate scripts and now the deployment worked. Hope this saves sometime for people out there who struggled like me
Thank you