-
Notifications
You must be signed in to change notification settings - Fork 7
missing atomix requirement #6
Comments
@paleozogt I think https://github.com/atomix/atomix-helm is the one you're looking for - this post also helped me back in the day: https://blog.zufardhiyaulhaq.com/install-onos-cluster-in-kubernetes/ |
@SamuAlfageme thanks for the pointer |
Hi, I have cloned the atomix-helm repo and changed the path for requirements.yaml to file://../../../atomix-helm/atomix . After that i was able to follow the steps provided in that link https//blog.zufardhiyaulhaq.com/install-onos-cluster-in-kubernetes/. But after running helm install as described in above step, the atomix pods are stuck in pending state and onos pods started running. After changing the minikube version to v1.12.0 this error disappeared but now i see that even all the pods for atomix and onos are in running state but the onos pods are getting restarted continuously after some time period and inside the onos logs i see the Storage TimeOut Execption during electing leader. Seems onos is not able to connect to atomix cluster. Please help me on this i am stuck in this issue for some time now! |
@ssks3092 I hit the same issue today, and this is my workaround if you're using
|
When I try to install I see an error:
Looking in requirements I see:
The path to
atomix-k8s
is out of this project. Where does it come from?The text was updated successfully, but these errors were encountered: