Skip to content

Conversation

@jaywcarman
Copy link
Member

When recording new VCR cassettes for #536 I encountered a strange response from the IBM Cloud resource controller API.

@jaywcarman jaywcarman requested review from Fryguy and agrare as code owners June 25, 2025 15:49
- close
response:
status:
code: 34
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have been unable to get a 34 response code when making this API call via curl and the same headers, etc.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opened a support ticket against the IBM Cloud resource controller service and they were able to find the transaction ID in their logs and verify that the original response code was 200.

I think the evidence points to something in the VCR recording code changing the response code:

  • I always get a 200 response when making the same API call (path, headers, etc.) using curl
  • I've tested this code live and it has never thrown and exception due to a 34 or any other weird response
  • When recording a new VCR tape of this API call I am always seeing a 34 response code.

Will continue to investigate.

@jaywcarman jaywcarman force-pushed the powervs_verify_credentials_spec branch from 3c6747c to bf23dd8 Compare July 7, 2025 20:10
The default IAM uri for power_virtual_servers is
'https://iam.cloud.ibm.com/identity/token#apikey'.

The resource controller URI starts with
'https://resource-controller.cloud.ibm.com' (no 'iaas' subdomain).
There's no harm in sanitizing _any_ domain with cloud.ibm in it.
@jaywcarman jaywcarman force-pushed the powervs_verify_credentials_spec branch from bf23dd8 to 023a569 Compare July 7, 2025 20:24
@miq-bot
Copy link
Member

miq-bot commented Jul 7, 2025

Checked commits jaywcarman/manageiq-providers-ibm_cloud@e4cbf7b~...023a569 with ruby 3.1.7, rubocop 1.56.3, haml-lint 0.64.0, and yamllint
2 files checked, 0 offenses detected
Everything looks fine. 🍪

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants