-
Notifications
You must be signed in to change notification settings - Fork 100
Failed to delete scratch org after validation #838
Comments
@rubiatoEJ It could be a erroneous log, Can you confirm whether the org is active in DevHub? |
@azlam-abdulsalam we are seeing the same thing, a scratch org taken from the pool cannot be deleted, seeing the same error here. Use latest SFDX CLI version |
@azlam-abdulsalam I have checked a latest failed PR validation as the previous org has already expired. this is the latest failed PR validation and failed to delete the scratch org I have asked to check if the org is active in DevHub and it shows as active |
Folks, this will need further investigation, as something with sfdx-cli 7.136.2 has changed. We advise all of you to rollback into |
@thvd @rubiatoEJ do you have the same issue with orgs fetched from developer pool? Locally everything works. :( |
@mshanemc any ideas here? |
@azlam-abdulsalam I have tried fetching from developer pool and delete with the same command used in validate and it shows that it is successfully deleted. Additional info: |
@aly76 I cant reproduce this locally, so it happens in docker image only. Probably the auth file is written to a plugin space? |
Fixed in 10.2.15 |
Describe the bug
When a PR validation is failed, an error also occurs that is unable to delete the scratch org.
When PR validation is successful, the deletion of scratch org after the run is successful as well.
I have checked this on every PR starting yesterday as the unusual error started yesterday, I noticed that it only occurs when a PR validation is failed.
I have attached the full raw logs as well.
Failed PR Validation (failed to delete scratchorg after validation).txt
Successful PR Validation (successful deletion of scratchorg after validation).txt
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When a PR validation is failed the deletion of scratch should not fail as well.
Screenshots
Failed PR validation:
Successful PR validation:
Platform Details (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: