Closed mikhailshilkov closed 4 months ago
Here's some initial thoughts on contributing factors:
read()
method which is used during the refresh. Therefore, we know in some context the read operation does work correctly. This leads me to think their is most likely a difference in:
cc: @alayshia @mikhailshilkov
I think the conclusion was that this was a problem with the customer's network configuration
What happened?
A customer is having an issue with one of their stacks. A
pulumi refresh
fails with the following error:This specific error is happening only on a pulumi refresh. It hangs for a long time during the refresh process (several minutes) before spitting out this error. Have confirmed that I can destroy and create using pulumi up and pulumi destroy with no issues.
In the detailed log, I see the following:
where it indicates that it failed to verify the x509 certificate
Example
Output of
pulumi about
CLI Version 3.106.0 Go Version go1.22.0 Go Compiler gc Plugins NAME VERSION azure 5.49.0 azure-native 2.32.0 azuread 5.40.0 command 0.7.2 docker 3.6.1 nodejs unknown random 4.13.2 Host OS Microsoft Windows 10 Enterprise Version 10.0.19045 Build 19045 Arch x86_64 This project is written in nodejs: executable='C:\Program Files\nodejs\node.exe' version='v18.14.2'
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).