https://pulumi.com logo
#general
Title
# general
s

straight-jordan-23612

08/22/2019, 12:46 AM
Copy code
pulumi:pulumi:Stack ff-data-import-lambda-dev running read pulumi:pulumi:StackReference factsfirstops/ff-infra/dev
    pulumi:pulumi:Stack ff-data-import-lambda-dev running TypeError: Cannot read property 'outputs' of undefined
Still have not found the answer to this one. Hard to debug the issue.
Copy code
Diagnostics:
  pulumi:pulumi:Stack (ff-data-import-lambda-dev):
    error: Running program '/builds/factsfirst/ff-data-import-lambda' failed with an unhandled exception:
    TypeError: Cannot read property 'outputs' of undefined
        at /builds/factsfirst/ff-data-import-lambda/node_modules/@pulumi/pulumi/stackReference.js:117:31
        at Generator.next (<anonymous>)
        at fulfilled (/builds/factsfirst/ff-data-import-lambda/node_modules/@pulumi/pulumi/stackReference.js:17:58)
        at <anonymous>
        at process._tickCallback (internal/process/next_tick.js:189:7)
        at Function.module.exports.loopWhile (/builds/factsfirst/ff-data-import-lambda/node_modules/deasync/index.js:70:11)
        at Object.promiseResult (/builds/factsfirst/ff-data-import-lambda/node_modules/@pulumi/pulumi/utils.js:80:13)
        at StackReference.getOutputSync (/builds/factsfirst/ff-data-import-lambda/node_modules/@pulumi/pulumi/stackReference.js:86:34)
        at Object.<anonymous> (/builds/factsfirst/ff-data-import-lambda/index.js:14:19)
        at Module._compile (module.js:653:30)
I am doing very little to cause this error. I basically reference a stack then call getOutputSync on a value and it throw it. I can not reproduce it locally but everytime a Gitlab runner runs it this is the result.
g

gentle-diamond-70147

08/22/2019, 4:32 AM
Hey Ben, this definitely doesn’t seem expected. Could you share your code with me? Email is fine if that’s best for you - cameron@pulumi.com.
s

straight-jordan-23612

08/22/2019, 4:38 AM
I figured it out
it is a bug with 1.0.0-beta
I reverted to 0.17 and it works
a

agreeable-apple-15721

08/22/2019, 1:37 PM
I'm getting exactly the same!
Joined the slack to see if anyone else was having the issue
It only happens on CircleCI (node docker), but not locally (on OSX)
Ahhhh - it's a bug in @pulumi/pulumi 1.0.0-beta.3
It's only happening on CI because my package.json specifies
latest
and my local version is at a different install
c

cool-egg-852

08/22/2019, 5:00 PM
Yeah, we just started running into this as well.
This is kind of a critical issue, hopefully they will have a version out soon
b

big-piano-35669

08/22/2019, 5:36 PM
We are looking into this -- goal is to get back ASAP.
cc @white-balloon-205
w

white-balloon-205

08/22/2019, 5:43 PM
This does appear to be a regression introduced in the latest
@pulumi/pulumi
1.0.0-beta.3
release along with https://github.com/pulumi/pulumi/issues/2744. For now, pinning to
1.0.0-beta.2
will workaround this. We'll get a fix in for this and release a
1.0.0-beta.4
shortly.
b

bitter-oil-46081

08/22/2019, 6:14 PM
I've opened a pull request: https://github.com/pulumi/pulumi/pull/3128 to address this. I'll post when 1.0.0-beta.4 is out.
a

agreeable-apple-15721

08/22/2019, 6:48 PM
c

cool-egg-852

08/22/2019, 6:51 PM
Thanks for the fix. Looking forward to the release (we pinned to .2 for now).
Always awesome work.
b

bitter-oil-46081

08/22/2019, 7:34 PM
1.0.0-beta.4
should be released now and
latest
should now point to it. Very sorry for the impact this caused ya'll.
c

cool-egg-852

08/22/2019, 7:51 PM
Is there a better way to install pulumi in CI then? We currently install it globally, and update it as needed.