You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
az feedback auto-generates most of the information requested below, as of CLI version 2.0.62
Describe the bug
When performing concurrent tests recently, we found that the generate_ssh_keys function provided by the cli core has potential concurrency conflicts.
In the existing implementation, when multiple processes try to create an ssh key, process A may have created a file but has not yet written key data, while process B reads an empty file at this time and obtains illegal empty key data.
In our module(acs/aks-preview), the example of calling this function is located in the validator.
For end users, this problem may also occur when users create multiple clusters (az aks create) at the same time and there is no ssh key that has been generated.
To Reproduce
Expected behavior
Environment summary
Additional context
A simple solution is to add a global lock to the generate_ssh_keys function.
The text was updated successfully, but these errors were encountered:
ghost
added
the
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
label
Jul 14, 2021
Describe the bug
When performing concurrent tests recently, we found that the
generate_ssh_keys
function provided by the cli core has potential concurrency conflicts.In the existing implementation, when multiple processes try to create an ssh key, process A may have created a file but has not yet written key data, while process B reads an empty file at this time and obtains illegal empty key data.
In our module(acs/aks-preview), the example of calling this function is located in the validator.
For end users, this problem may also occur when users create multiple clusters (
az aks create
) at the same time and there is no ssh key that has been generated.To Reproduce
Expected behavior
Environment summary
Additional context
A simple solution is to add a global lock to the
generate_ssh_keys
function.The text was updated successfully, but these errors were encountered: