Is it normal to get a bunch of "unhandled rejectio...
# automation-apil
limited-rain-96205
05/12/2021, 3:21 AMIs it normal to get a bunch of "unhandled rejection" errors when the inline program doesn't return all of the resources created? In other words, it is a requirement to output all resources?
l
lemon-agent-27707
05/12/2021, 3:24 AMNo. That sounds similar to this bug that was reported in the last few days: https://github.com/pulumi/pulumi/issues/6998
lemon-agent-27707
05/12/2021, 3:25 AMIf you're facing the same error, would you mind dropping some notes and/or a repro in the issue?
l
limited-rain-96205
05/12/2021, 3:25 AMThe errors I'm getting are a little different. They look like this:
Copy code
build 11-May-2021 20:19:54 unhandled rejection: CONTEXT(137): resource:sordino[kubernetes:<http://networking.istio.io/v1alpha3:VirtualService|networking.istio.io/v1alpha3:VirtualService>]
build 11-May-2021 20:19:54 STACK_TRACE:
build 11-May-2021 20:19:54 Error
build 11-May-2021 20:19:54 at Object.debuggablePromise (/pulumi-repo/node_modules/@pulumi/kubernetes/node_modules/@pulumi/pulumi/runtime/debuggable.js:69:75)
build 11-May-2021 20:19:54 at Object.registerResource (/pulumi-repo/node_modules/@pulumi/kubernetes/node_modules/@pulumi/pulumi/runtime/resource.js:220:18)
build 11-May-2021 20:19:54 at new Resource (/pulumi-repo/node_modules/@pulumi/kubernetes/node_modules/@pulumi/pulumi/resource.js:215:24)
build 11-May-2021 20:19:54 at new CustomResource (/pulumi-repo/node_modules/@pulumi/kubernetes/node_modules/@pulumi/pulumi/resource.js:307:9)
build 11-May-2021 20:19:54 at new CustomResource (/pulumi-repo/node_modules/@pulumi/apiextensions/customResource.ts:91:9)
build 11-May-2021 20:19:54 at new VirtualService (/pulumi-repo/node_modules/@bluenile/pulumi-kubernetes-istio/sdk/nodejs/src/v1_7/networking/v1alpha3/virtual-service.ts:20:5)
build 11-May-2021 20:19:54 at new AppDeployment (/pulumi-repo/node_modules/@bluenile/pulumi-shared/src/k8s/app-deployment.ts:193:31)
build 11-May-2021 20:19:54 at new DevOpsDeployment (/pulumi-repo/src/devops/index.ts:19:30)
build 11-May-2021 20:19:54 at DeploymentManager.<anonymous> (/pulumi-repo/src/deployment-manager.ts:206:20)
build 11-May-2021 20:19:54 at Generator.next (<anonymous>)limited-rain-96205
05/12/2021, 3:26 AMThe weird thing is, it spams these repeatedly after Pulumi has "successfully" done a preview with no errors.
l
lemon-agent-27707
05/12/2021, 3:27 AMThat kinda sounds like a dropped dependency somewhere. The pulumi engine things the preview is done but there is outstanding work in the node runtime.
lemon-agent-27707
05/12/2021, 3:28 AMWould you mind opening an issue with a repro and the full error message? (sorry about the verbose errors, hopefully this was improved by https://github.com/pulumi/pulumi/pull/6995 which should be released next week).
lemon-agent-27707
05/12/2021, 3:29 AMAlso include info about the version of the CLI and nodejs SDK you're using if you don't mind.
l
limited-rain-96205
05/12/2021, 3:33 AMYeah, in the inline program if I return an object which contains all of the resources created, all of these errors go away. Without that it's like it's not waiting for resources to finish.
limited-rain-96205
05/12/2021, 3:33 AMI'll open an issue
b
busy-honey-73811
05/12/2021, 8:47 PMMaybe it is related to https://github.com/pulumi/pulumi/issues/7017 as discussed in https://pulumi-community.slack.com/archives/C84L4E3N1/p1620649793472000.
l
limited-rain-96205
05/12/2021, 9:01 PMI don't think it's an importing issue. I'm instantiating the objects fine, it's just that unless they're returned in the async function, Pulumi doesn't wait for resources before finishing.
limited-rain-96205
05/12/2021, 9:02 PMI've found a workaround which just involves returning an empty dummy resource that depends on the main one.
11 Views