Open SaiKumarNerella opened 2 years ago
Do the artifacts appear on OCI object store (do they actually get written?)
Yes
I'm facing the same issue with version 1.26.1
@BenWilson2 @harupy Any updates here?
I've added the help wanted
label, as it would be very helpful to get community assistance root causing and fixing this issue. Thank you!
Hi folks!
In my case, the host (App Runner) was using a VPC that doesn't have a VPC Endpoint configured to Amazon S3. I added it and the issue was fixed.
we had a similar issue on mlflow==1.29.0
but it was because of wrong artifact location. S3 path was erroneous: ss3://path/to/object
. After fixing it to s3://path/to/object
all works fine.
Thank you for submitting an issue. Please refer to our issue policy for additional information about bug reports. For help with debugging your code, please refer to Stack Overflow.
Please fill in this bug report template to ensure a timely and thorough response.
Willingness to contribute
The MLflow Community encourages bug-fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the MLflow code base?
System information
mlflow --version
): 1.24.0Describe the problem
Describe the problem clearly here. Include descriptions of the expected behavior and the actual behavior.
Articrafts Tab on the Run Details page failed to load the articrafts from the oracle cloud object storage.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
What component(s), interfaces, languages, and integrations does this bug affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrations