search

fabric8-services / fabric8-wit

wit stands for Work Item Tracker
http://devdoc.almighty.io/
Apache License 2.0
45 stars 86 forks source link

/api/user/services does not return namespace info for some users: #2338

Closed ibuziuk closed 5 years ago

ibuziuk commented 5 years ago

curl -k -H "Authorization: Bearer <TOKEN>" https://api.prod-preview.openshift.io/api/user/services | jq '.' returns the following response for 9349415e-21b8-43e9-a3dd-31079b02d61a1 : 

{
  "data": {
    "attributes": {
      "created-at": "2018-10-29T12:19:20.369725Z"
    },
    "id": "9349415e-21b8-43e9-a3dd-31079b02d61a",
    "type": "userservices"
  }
}

All the namespaces info are missing, is missing event hough namespaces have been provisioned correctly on oso side:

image

This error prevents che workspace to start for the user since we fall back on this API in particular for checking cluster-capacity-exhausted flag.

ibuziuk commented 5 years ago

cc: @aslakknutsen @alexeykazakov

ScrewTSW commented 5 years ago

Original account creation issue handled by @dipak-pawar https://gitlab.cee.redhat.com/dtsd/housekeeping/issues/2410

alexeykazakov commented 5 years ago

@MatousJobanek can you please take a look at this user/namespaces?

ScrewTSW commented 5 years ago

Hello guys, the issue is still present.

che-master logs: https://pastebin.com/tqRARnCr auth logs: https://pastebin.com/edit/qh8GBCSk

nothing in events on starter cluster, pod was never created.

ScrewTSW commented 5 years ago

bump @alexeykazakov @MatousJobanek

MatousJobanek commented 5 years ago

Just working on fixing the account setup. Today I didn't make it running - unfortunately, OpenShift still complains about conflicts even though there is no namespace with such a name. I'll continue tomorrow

ScrewTSW commented 5 years ago

resolved. toggle was set to single-tenant. reset environment fixed the issue

MatousJobanek commented 5 years ago

That the toggle deploy.che-multi-tenant was disabled was part of the whole problem. But as @ScrewTSW has already mentioned, reset of the whole tenant environment (plus a few additional steps) helped and the account is working correctly. Closing this issue...