kubeflow: Looping "Could not find namespace kubeflow-anonymous, wait and retry" on initial apply
/kind bug
What steps did you take and what happened:
Ran kfctl apply all
as per instructions in https://www.kubeflow.org/docs/started/k8s/kfctl-k8s-istio/.
Operation did not exit but looped with these messages:
WARN[0474] Could not find namespace kubeflow-anonymous, wait and retry: namespaces "kubeflow-anonymous" not found filename="kustomize/kustomize.go:353"
WARN[0506] Could not find namespace kubeflow-anonymous, wait and retry: namespaces "kubeflow-anonymous" not found filename="kustomize/kustomize.go:353"
WARN[0547] Could not find namespace kubeflow-anonymous, wait and retry: namespaces "kubeflow-anonymous" not found filename="kustomize/kustomize.go:353"
What did you expect to happen:
I expected the command to exit successfully having applied the config.
Environment:
- Kubeflow version: (version number can be found at the bottom left corner of the Kubeflow dashboard): I don’t have this running yet - how is this different from version printed by
kfctl
? - kfctl version:
kfctl v0.6.2-0-g47a0e4c7
- Kubernetes platform: microk8s
- Kubernetes version:
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.6", GitCommit:"abdda3f9fefa29172298a2e42f5102e777a8ec25", GitTreeState:"clean", BuildDate:"2019-05-08T13:53:53Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.6", GitCommit:"abdda3f9fefa29172298a2e42f5102e777a8ec25", GitTreeState:"clean", BuildDate:"2019-05-08T13:46:28Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
- OS: Linux 4.15.0-58-generic #64-Ubuntu SMP
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 31 (11 by maintainers)
You can create
kubeflow-anonymous
namespace in advance.Here’s how I was able to resolve this one on my end.
If ever you have already applied do this:
istio-system
namespace from Kubernetes — so that the error on Port already being used won’t happenkubeflow-anonymous
If ever you’re just going to start initializing, download the config files first and then add the
kubeflow-anonymous
namespace.Hope this helps someone. Props to: @wzxJayce
Issue-Label Bot is automatically applying the label
kind/bug
to this issue, with a confidence of 0.99. Please mark this comment with 👍 or 👎 to give our bot feedback!Links: app homepage, dashboard and code for this bot.
same issue:
@wzxJayce , you saved my day
Is there any new info on this? I am also seeing the same error running on an EKS cluster on AWS. I am following the steps here: https://www.kubeflow.org/docs/aws/deploy/install-kubeflow/ . I am seeing the error occur on the “apply” step: kfctl apply all -V. And it does not appear to be a warning. The process does eventually terminate with the following error after retrying for about 15 mins.
couldn’t apply KfApp: (kubeflow.error): Code 500 with message: kfApp Apply failed for kustomize: (kubeflow.error): Code 400 with message: Could not find namespace kubeflow-anonymous, wait and retry: Get https://2D737A4E4A13EBC879857AB7571B0E38.gr7.us-east-1.eks.amazonaws.com/api/v1/namespaces/kubeflow-anonymous: write tcp 10.0.0.250:50495->3.229.9.250:443: write: can’t assign requested address
@gar1t I believe that you saw this message during apply, not generate. Can you confirm?
This is more of a UX issue than a bug. The kfctl code is waiting for the default namespace to be created before exiting.
However the code should be of LogLevel info and not warn, since it is not an abnormal condition.
In addition, I feel that the wording should be different to convey that this is a normal part of the installation. The current wording makes it seem like there is something wrong. How about:
Waiting for default Profile namespace (kubeflow-anonymous) to be created...