Open douglasg14b opened 4 months ago
iwahbe
commented
4 months ago Hey @douglasg14b. I'm sorry you're hitting that, it looks like something has gone wrong here. If you could provide us a program that reproduces the panic, we would be happy to take a look.
Unfortunately, it's very hard for us to fix the problem if we can't reproduce it.
douglasg14b
commented
4 months ago I'm having trouble reproing this anywhere else. Is there more information I might be able to provide that may lead to this being more approachable by you or your team?
iwahbe
commented
3 months ago Sorry for the long wait time. If you run PULUMI_DEBUG_GRPC=logs.json pulumi up, then send us the resulting logs.json file that could help.
That json file might contain secrets, depending on how you have configured your provider. Make sure to scrub those.
mdegel
commented
3 months ago Might be unrelated, but I had a similar issue with pulumi-artifactory (Python):
With pulumi_artifactory==6.5.1 I get similar errors:
$ pulumi up
# ...
artifactory:index:LocalGenericRepository (demo-staging-generic-local):
error: error reading from server: read tcp 127.0.0.1:60632->127.0.0.1:60629: wsarecv: An existing connection was forcibly closed by the remote host.Reverting to an older version pulumi_artifactory==6.4.5 yields actually more information about then real issue:
$ pulumi up
# ...
artifactory:index:LocalGenericRepository (demo-staging-generic-local):
error: 1 error occurred:
*
400 PUT https://my.url.com/artifactory/api/repositories/demo-staging-generic-local
{
"errors" : [ {
"status" : 400,
"message" : "This REST API is available only in Artifactory Pro (see: jfrog.com/artifactory/features). If you are already running Artifactory Pro please make sure your server is activated with a valid license key.\n"
} ]
}In my case the newer versions of the generated pulumi libraries started hiding the actual internal errors (which themselves are unrelated to pulumi). Might be a similar issue here with unexpected responses from digitalocean?
douglasg14b
commented
1 month ago @iwahbe
This happens when i have an app spec with CORS rules (Which even has a placeholder example header 😅):
When the CORS rules are removed, this issue no longer occurs.
new digitalocean.App('[REDACTED]', {
spec: {
name: '[REDACTED]',
region: digitalocean.Region.NYC3,
databases: [{
name: '[REDACTED]',
clusterName: '[REDACTED]',
dbName: '[REDACTED]',
dbUser: '[REDACTED]',
production: true,
}],
services: [{
name: '[REDACTED]',
instanceSizeSlug: 'professional-xs',
github: {
branch: '[REDACTED]',
repo: '[REDACTED]',
deployOnPush: false,
},
sourceDir: '[REDACTED]',
dockerfilePath: '[REDACTED]',
httpPort: 8080,
}],
staticSites: [{
name: 'client-app',
dockerfilePath: 'Dockerfile.client',
outputDir: '/app',
github: {
branch: '[REDACTED]',
repo: '[REDACTED]',
deployOnPush: false,
},
catchallDocument: 'index.html',
}],
ingress: {
rules: [
{
component: {
name: '[REDACTED]',
preservePathPrefix: true,
},
match: {
path: {
prefix: '/api',
},
},
cors: {
allowMethods: ['GET', 'POST', 'PUT', 'DELETE'],
allowHeaders: ['*'],
exposeHeaders: ['X-My-Custom-Header'],
allowCredentials: false,
},
},
{
component: {
name: 'client-app',
},
match: {
path: {
prefix: '/',
},
},
},
],
},
},
});Hey @douglasg14b. Thanks for the repro. Amazingly, the code you gave actually works as given (except the reference to the free variable envs, which can be removed).
For a simplified repro:
import * as digitalocean from "@pulumi/digitalocean";
new digitalocean.App('[REDACTED]', {
spec: {
name: '[REDACTED]',
region: digitalocean.Region.NYC3,
ingress: {
rules: [
{
cors: {
allowMethods: ['GET', 'POST', 'PUT', 'DELETE'],
},
},
],
},
},
});I have confirmed that this is a bug upstream and have opened an issue there: https://github.com/digitalocean/terraform-provider-digitalocean/issues/1176. We will take the fix as soon as they do.
douglasg14b
commented
1 month ago Interesting, thank you for finding & confirming the issue.
What happened?
When I try an run
puluumi upfrom a rpeviously working configuration. I get the following exception:Example
Unknown, this started happening out of the blue. I don't know how to repro it, or where I would even start.
Output of
pulumi aboutAdditional context
My deployments where working, but not they do not. Unsure if this is a local machine problem, or a problem with pulimi? Either way, there's probably a location here for error handling.
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).