minishift: Namespace myproject doesn't exist

I’ve been trying to figure out the root of this problem for the past 2 days so I’m going to be as specific as possible.

All I am trying to do is run this command as part of the quickstart guide:

minishift openshift service nodejs-ex -n myproject

Short story:

I followed the guide exactly and everything works except this command.

Long story:

I’m on OSX and have tried using both virtualbox and xhyve as my hypervisor. Initially I tried virtualbox, but they both resulted in the same behavior. I’m running Minishift version: 1.0.0 (but have tried the beta as well). Initially, when I install minishift, what will happen is I run the command:

$ minishift start

Everything will seem fine, but then I’ll be greeted with this error:


...
 Starting OpenShift using container 'origin'
   Waiting for API server to start listening
FAIL
   Error: cannot access master readiness URL https://192.168.64.2:8443/healthz/ready
   Details:
     Last 10 lines of "origin" container log:
     E0519 19:51:02.324286    2739 reflector.go:199] github.com/openshift/origin/vendor/k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:103: Failed to list *api.ServiceAccount: User "system:openshift-master" cannot list all serviceaccounts in the cluster
     E0519 19:51:02.324589    2739 reflector.go:199] github.com/openshift/origin/vendor/k8s.io/kubernetes/plugin/pkg/admission/resourcequota/resource_access.go:83: Failed to list *api.ResourceQuota: User "system:openshift-master" cannot list all resourcequotas in the cluster
     E0519 19:51:02.324805    2739 reflector.go:199] github.com/openshift/origin/vendor/k8s.io/kubernetes/plugin/pkg/admission/storageclass/default/admission.go:75: Failed to list *storage.StorageClass: User "system:openshift-master" cannot list all storage.k8s.io.storageclasses in the cluster
     E0519 19:51:02.467733    2739 reflector.go:199] pkg/controller/informers/factory.go:89: Failed to list *api.Namespace: User "system:openshift-master" cannot list all namespaces in the cluster
     E0519 19:51:02.480105    2739 reflector.go:199] pkg/controller/informers/factory.go:89: Failed to list *api.LimitRange: User "system:openshift-master" cannot list all limitranges in the cluster
     E0519 19:51:02.480277    2739 reflector.go:199] github.com/openshift/origin/pkg/controller/shared/shared_informer.go:89: Failed to list *api.SecurityContextConstraints: User "system:openshift-master" cannot list all securitycontextconstraints in the cluster
     E0519 19:51:02.483918    2739 reflector.go:199] github.com/openshift/origin/pkg/controller/shared/shared_informer.go:89: Failed to list *api.ImageStream: User "system:openshift-master" cannot list all imagestreams in the cluster
     E0519 19:51:02.484146    2739 reflector.go:199] pkg/controller/informers/factory.go:89: Failed to list *api.ServiceAccount: User "system:openshift-master" cannot list all serviceaccounts in the cluster
     E0519 19:51:02.551654    2739 reflector.go:199] github.com/openshift/origin/pkg/controller/shared/shared_informer.go:101: Failed to list *api.ClusterResourceQuota: User "system:openshift-master" cannot list all clusterresourcequotas in the cluster
     E0519 19:51:02.554021    2739 reflector.go:188] github.com/openshift/origin/pkg/project/cache/cache.go:107: Failed to list *api.Namespace: User "system:openshift-master" cannot list all namespaces in the cluster


Error starting the cluster.

At this point, the UI is running and I can access https://192.168.64.2:8443 with my browser. If I run minishift start again, I won’t get any errors, and I’ll get this success message:


   You are logged in as:
       User:     developer
       Password: developer

   To login as administrator:
       oc login -u system:admin

If I run minishift stop and then minishift start again, I get the success message:

  To login as administrator:
       oc login -u system:admin

Then after this, everything seems normal, everything works fine. Except for the fact that I can’t run:

minishift openshift service nodejs-ex -n myproject

I get the message:

Namespace myproject doesn't exits

I feel like I have tried everything, any ideas?

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 2
Comments: 28 (18 by maintainers)

Most upvoted comments

There is no update from reporter (waited around 4 days). Going to close this issue now.

praveenkumar on Aug 8, 2017

As bootstraping of the cluster has not worked, the project “myproject” has not been created, hence all the errors.

To fix it it would require to run “oc new-project myproject”, but I would rather investigate why the bootstrapping failed.

Are you on a really slow internet connection? Are you being a proxy or vpn? Could you probably recreate the VM? “minishift delete && minishift start”? Note that this might take a while since some images will need to be pulled down. Are you limiting the amount of cpu or memory? Can you start with some log level enabled? (Not sure the exact command but there’s plenty of references in this forums).

With this we could probably try to diagnose the real underlying error rather than fixing and hiding what could be a bug.

jorgemoralespou on May 21, 2017