-
Notifications
You must be signed in to change notification settings - Fork 1.5k
IBMCloud: Use unique mutex for Client retrieval #6241
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
IBMCloud: Use unique mutex for Client retrieval #6241
Conversation
|
/assign @rvanderp3 |
|
/hold |
|
/assign |
A shared mutex for all ibmcloud.metadata functions, including the public Client method, deadlocks calls. Since the Client is a public method, we should still use a mutex, but it should be a unique mutex to prevent deadlocking.
|
Will retest once I push up changes recommended with mutex |
ae4d5ee to
61ff6c8
Compare
|
Install worked as expected Failure due to conformance tests, which is currently expected |
|
/hold cancel |
|
@jstuever this should be ready for your |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jstuever The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test yaml-lint |
|
/test aro-unit |
|
@cjschaef: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
A shared mutex for all ibmcloud.metadata functions, including the
public Client method, deadlocks calls. Since the Client is a public
method, we should still use a mutex, but it should be a unique
mutex to prevent deadlocking.