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 trying to deploy I noticed that the install script sometimes fails silently.
Running ./install-kubeflow.sh stopped after "Creating Kubeflow app directory:<>" without any errors.
After debugging I found out that somehow my proxy stopped. Therefore the s pull for the swagger.json from GitHub in
The script is run with "set -e", which should show any error. This feels like a silent error in the underlying kfctl.sh script. That script is evolving into a go binary. Let's wait until that work is done and we'll integrate with that, hopefully in the 0.5.0 timeframe.
Thanks for your answer.
Is there a fixed release cycle for kubeflow or a planned release date for 0.5.0 already?
The Proxy I use is a custom CNTLM-Proxy, wich somehow always stops working in the middle of running the script. (Pulling and wget works fine, but pulling the swagger.json from GitHub fails)
While trying to deploy I noticed that the install script sometimes fails silently.
Running
./install-kubeflow.sh
stopped after "Creating Kubeflow app directory:<>" without any errors.After debugging I found out that somehow my proxy stopped. Therefore the s pull for the swagger.json from GitHub in
kubeflow-tools/install-kubeflow.sh
Line 85 in d5e73b3
didn't work. Is there any way to not silently fail here?
(Running the it again brought up:
ERROR could not finde component: extracting module and component names from ambassador...
)The text was updated successfully, but these errors were encountered: