Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Cannot create a space on the default organization as admin user on new CF #9

Open
drnic opened this issue Jun 12, 2013 · 6 comments
Open

Comments

@drnic
Copy link
Contributor

drnic commented Jun 12, 2013

When you target a new CF, which has no organizations nor spaces, the CLI currently prompts you (helpfully) to create a space. It fails to create a space on the default organization.

@dmrschmidt
Copy link
Contributor

That's a good point. However you would have to be an admin user to even be able to create a new org. Maybe we should instead show a helpful message to the user on how to proceed?

@drnic
Copy link
Contributor Author

drnic commented Jun 14, 2013

Reproduction of scenario on a fresh CF using admin credentials:

$ cf target api.drniccloud.com
Setting target to http://api.drniccloud.com... OK

target: http://api.drniccloud.com


$ cf login
target: http://api.drniccloud.com

Email> admin

Password> ****************

Authenticating... FAILED
Password> ********

Authenticating... OK
There are no spaces. You may want to create one with create-space.


$ cf create-space
Name> foobar

Creating space foobar... OK
Adding you as a manager... FAILED
CFoundry::InvalidRelation: 1002: Invalid relation: 0f11652d-2447-4b21-8b27-e0528406c5a0
For more information, see ~/.cf/crash

@drnic
Copy link
Contributor Author

drnic commented Jun 14, 2013

$ cf orgs
Getting organizations... OK

name         spaces   domains
drniccloud   foobar   none   


$ cf org
drniccloud:
  domains: none
  spaces: foobar

So it looks like I do have an org, and it is selected, but I get the error above when creating a space.

@drnic
Copy link
Contributor Author

drnic commented Jun 14, 2013

Updated ticket title/description

@PavelKovalets
Copy link

I have the same error message and it is really confusing because the spaces is actually created

@jfoley
Copy link

jfoley commented Aug 14, 2013

@drnic - We have had similar experiences and we are pinging the @tlang to see what the current thinking about a fix is.

@aramprice / @jfoley

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants