403 error when logging in with OC on openshift adb

[kferrone]

For the life of me I can't figure out how to get oc login to work right after the initial install of the adb-openshift with vagrant.

Host OS: MacOS High Sierra 10.13.4
VM: VirtualBox 5.2.10 r122088 (Qt5.6.3)
Provisioner: Vagrant 2.0.4
CLI: oc v3.9.0+191fece
Vagrant Plugins: vagrant-service-manager, vagrant-sshfs, landrush, vagrant-registration, vbguest

Here are the steps I take:

• mkdir -p adb
• cd adb
• curl -sL https://raw.githubusercontent.com/projectatomic/adb-atomic-developer-bundle/master/components/centos/centos-openshift-setup/Vagrantfile > Vagrantfile
• vagrant up
• eval "$(vagrant service-manager env)"
• oc login https://172.28.128.3:8443

Then I get this error:

error: couldn't get https://172.28.128.3:8443/.well-known/oauth-authorization-server: unexpected response status 403

Same error in the browser:https://172.28.128.3:8443/.well-known/oauth-authorization-server

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "User \"system:anonymous\" cannot \"get\" on \"/.well-known/oauth-authorization-server\"",
  "reason": "Forbidden",
  "details": {},
  "code": 403
}

Some things I tried and found out:

• trust every friggin key I could possibly find in my mac keyring
• googled a ton and nada
• maybe something to do with the registry
• I also tried minishift and minikube before this. Could these conflict somehow?
• tried this too: oc login https://172.28.128.3:8443 -u system:admin -p admin
• haven't tried yet but I will try to map all needed ports to localhost on host but this seems unnecessary

I did add some custom options to the Vagrantfile like below but not the whole file, you get the idea.

VM_NAME = "adb_openshift"

config.vm.define VM_NAME

#enable services for IDE use
config.servicemanager.services = 'docker, openshift'
config.servicemanager.openshift_docker_registry = DOCKER_REGISTRY
config.servicemanager.openshift_image_name = IMAGE_NAME
config.servicemanager.openshift_image_tag = IMAGE_TAG

v.name = VM_NAME

Another strange note about running vagrant service-manager status

Configured services:
docker - running
openshift - running
kubernetes - stopped

I see kubernetes is stopped so I ran vagrant service-manager start kubernetes and got:

Configured services:
docker - running
openshift - stopped
kubernetes - running

Why does enabling kubernetes stop openshift and vice-versa??? Does this have something to do with my issues???