Add PowerVS verify credentials spec#537
Conversation
| - close | ||
| response: | ||
| status: | ||
| code: 34 |
There was a problem hiding this comment.
I have been unable to get a 34 response code when making this API call via curl and the same headers, etc.
There was a problem hiding this comment.
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
200response when making the same API call (path, headers, etc.) usingcurl - I've tested this code live and it has never thrown and exception due to a
34or any other weird response - When recording a new VCR tape of this API call I am always seeing a
34response code.
Will continue to investigate.
.../manageiq/providers/ibm_cloud/power_virtual_servers/cloud_manager/verify_credentials_spec.rb
Outdated
Show resolved
Hide resolved
jaywcarman
force-pushed
the
powervs_verify_credentials_spec
branch
from
3c6747c to
bf23dd8
Compare
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
force-pushed
the
powervs_verify_credentials_spec
branch
from
bf23dd8 to
023a569
Compare
|
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 |
|
This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the |
4 participants
When recording new VCR cassettes for #536 I encountered a strange response from the IBM Cloud resource controller API.