You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While going through the watson example I noticed the following errors:
The Kubernetes serviceaccount pipeline-runner has no rights to create secrets (affected line).
All labels in the component.yaml are not allowed values (IBM Watson Machine Learning). Space characters are not allowed.
wml-train.py needs the cos_endpoint in two different formats. Minio needs the endpoint without scheme (https://) and the model metadata connection endpoints (line) needs the endpoint with scheme. More specific error occurs at the attempt to monitor the training run (line)
Due to assumption that the input parameter is created in wm-train.py, the sample will not work any more. The output of the config step will not return "created". Additional is the order of the input parameter in the train step is incorrect.
Locally I was able to fix all of this bugs. If I should create a pull request let me know. @animeshsingh and @Ark-kun I think this issue is interesting for you.
The text was updated successfully, but these errors were encountered:
@mpoqq there is PR pending merge 2, 4, and in our deployments by default we give increased permissions to pipeline runner. Once that PR is merged will be good to get to get yours on top #1246
While going through the watson example I noticed the following errors:
IBM Watson Machine Learning
). Space characters are not allowed.cos_endpoint
in two different formats. Minio needs the endpoint without scheme (https://) and the model metadata connection endpoints (line) needs the endpoint with scheme. More specific error occurs at the attempt to monitor the training run (line)created
in wm-train.py, the sample will not work any more. The output of the config step will not return "created". Additional is the order of the input parameter in the train step is incorrect.Locally I was able to fix all of this bugs. If I should create a pull request let me know.
@animeshsingh and @Ark-kun I think this issue is interesting for you.
The text was updated successfully, but these errors were encountered: