Closed balakrishnangithub closed 8 years ago
@bkmagnetron I'm not sure this is a bug, the origin-clients package ships a kubectl binary just as the kubernetes-client package does.
We could potentially make the error message friendlier, but they are two conflicting packages.
@detiber My bad!!! I forgot that I've installed Cockpit with Kubernetes. I removed it then there was no error in installation. Even though installation was successfully I'm facing issue when deploying application. I'm getting error like no node is available for the pod. I think there is something to do with Kubernetes.
Do I have to close this issue and create a new issue for that?
@bkmagnetron That might be a better discussion for the mailing lists: https://lists.openshift.redhat.com/openshiftmm/listinfo
That said, you should be able to do an oc describe dc <name of dc>
and oc describe pod <name of pod>
to get further information about why the scheduling is failing.
Ansible hosts file:
Install:
# ansible-playbook openshift-ansible/playbooks/byo/config.yml
Ansible Error: