IBM-Cloud / IBM-Cloud/ibm-cloud-cli-release

'ibmcloud account org-user-remove' with the account owner weird behavior

Open
#63 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
160
Forks
74
PR merge metrics
No merged PRs in 30d

Description

Hi there,

When I run the command: 'ibmcloud account org-user-remove ORG -f', it revokes the access to that ORG because you cannot see the ORG anymore with both the CLI and the WEB (console.bluemix.net), although it seems to be that ORG exists already somewhere.. As mentioned, the user should be the account owner.

Steps to reproduce it:

  • Use the account owner user. ibmcloud version: 0.11.0
  • Create an ORG, let's say 'dev-team-org'
  • Create an space, let's say 'dev-space-org'
  • Add some other members to the team, roles are indifferent
  • Run as account owner -> 'ibmcloud account org-user-remove dev-team-org -f'
  • When it finished, run 'ibmcloud account orgs' and the ORG is gone. Go to the WEB and double check.
  • Try to create the ORG again, run 'ibmcloud account org-create dev-team-org'
  • You will get "Error response from server. Status code: 409; description: Organization cannot be created because it already exists"

When you try to delete user-policies to the account owner (IAM) you got a warning saying that you cannot revoke permissions to the owner, even if you run the command as owner.

What can I do to delete the ORGs created definitively or recover them?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior with ibmcloud version 0.11.0 using the commands ibmcloud account org-user-remove, orgs, and org-create described in the issue. Check the CLI and web console after removing the account owner, then verify that the organization remains accessible or can be definitively deleted and recreated without the 409 response.

Written by the indexing model from the issue text.

Assessment

Tech stack
cloud
Domain
cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.