Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting 500 internal error in ibm_account table #118

Closed
bigdatasourav opened this issue Mar 1, 2024 · 2 comments · Fixed by #120
Closed

Getting 500 internal error in ibm_account table #118

bigdatasourav opened this issue Mar 1, 2024 · 2 comments · Fixed by #120
Assignees
Labels
bug Something isn't working

Comments

@bigdatasourav
Copy link
Contributor

Describe the bug

 select
  name,
  guid as id,
  state,
  owner_user_id
from
  ibm_account;

Error: ibm: Request failed with status code: 500, internal_error:
@bigdatasourav bigdatasourav added the bug Something isn't working label Mar 1, 2024
@bigdatasourav bigdatasourav self-assigned this Mar 1, 2024
@ParthaI ParthaI assigned ParthaI and unassigned bigdatasourav Mar 8, 2024
@ParthaI
Copy link
Contributor

ParthaI commented Mar 8, 2024

We're following the guidelines specified in the SDK documentation for making the API call. Unfortunately, the error seems to stem from the SDK during the creation of the Account Client, prior to initiating the API call. I've submitted a support request to the IBM Cloud SDK team to resolve this matter. We will circle back to this issue upon receiving feedback from the IBM Cloud SDK support team. Thank you!

For reference, here is the link to the support request: IBM Cloud SDK Support Request.

@ParthaI ParthaI added the blocked Work on this issue is currently blocked label Mar 8, 2024
@ParthaI
Copy link
Contributor

ParthaI commented Mar 15, 2024

This will be addressed once the following PR is merged:

Ref: IBM-Cloud/bluemix-go#435

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants