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

[jmgalvez]

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?

[boyang9527]

'ibmcloud account org-user-remove` will not remove the org. Can you post the full log?

[jmgalvez]

I do not have the full log, long time ago... anyway, if you follow the steps above it is relatively easy to reproduce.
yes, correct, org is not removed, but it is not visible for the user anymore. Currently I have an open support ticket regarding this issue.

With regards to deletion, I engaged IBM Technical Support in order to delete the ORGs and RGs, but they declined to do it. They told me that they are not doing this deletion anymore (previously they did it).

[Debasis8280]

Error response from server. Status code: 409; description: The following error occurred in the region 'Dallas' ??...

[steveclay]

@Debasis8280 is your comment related to this original issue or are you seeing another issue?