cf mgmt Pipeline to update-space-user is failing
niteshpa opened this issue · 5 comments
Error syncing users for org xxx, space test, role developer: adding ldap users: User xxxxx with origin ldap: cfclient error (CF-UnprocessableEntity|10008): User 'xxxxx' already has 'space_developer' role in space 'test'.]
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
@niteshpa This issue should have been fixed in 1.0.85 - https://github.com/vmware-tanzu-labs/cf-mgmt/releases/tag/v1.0.85 let me know if this is persisting once you have updated to this version or beyond.
We upgraded to 1.0.85, but still this issue is persisting.
@niteshpa will need you to provide full debug and trace output to further triage this. This can be done by setting LOG_LEVEL to debug and in a different run set it to trace. Debug provides cf-mgmt level logging and trace provides raw http request / response information. If unable to cleanse the data and a VMware / Broadcom customer can open a support ticket and upload the information which I can then retrieve it.
Other alternative is to delete this user and see if this resolves the problem with “cf delete-user” command
Please validate this against latest version - https://github.com/vmware-tanzu-labs/cf-mgmt/releases/tag/v1.0.88 as this should resolve these issues due to other performance related issues with uaa and cloud controller being fixed in TAS releases. Once upgrade if these issues persist please open a fresh issue to track this.