https://pulumi.com logo
Join Slack
Powered by
i'm working on an orchestration container that has...
# general
b
i'm working on an orchestration container that has pulumi, az-cli, aws-cli, terraform, bunch of binaries in a controlled environment with authentication through env vars etc.. anyways, i found that if you 
npm install
inside docker, and then on my host macOS, it complains about the version of gRCP.. however, while developing, I found that if you 
pulumi up
with the wrong one in place, apparently it deletes everything. Since this is for automation, I added a 
-y
to my 
pulumi up
command, but what i got was a full destroy. Probably not a bug, per se, but thinking you guys should be aware.
Copy code
Diagnostics:
  pulumi:pulumi:Stack (compute-b-compute-b-stage-eus2):
    (node:97) UnhandledPromiseRejectionWarning: Error: Failed to load gRPC binary module because it was not installed for the current system
    Expected directory: node-v64-linux-x64-glibc
    Found: [node-v64-darwin-x64-unknown]
    This problem can often be fixed by running "npm rebuild" on the current system
    Original error: Cannot find module '/data/pulumi/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc/grpc_node.node'
        at Object.<anonymous> (/data/pulumi/node_modules/grpc/src/grpc_extension.js:53:17)
        at Module._compile (internal/modules/cjs/loader.js:689:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
        at Module.load (internal/modules/cjs/loader.js:599:32)
        at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
        at Function.Module._load (internal/modules/cjs/loader.js:530:3)
        at Module.require (internal/modules/cjs/loader.js:637:17)
        at require (internal/modules/cjs/helpers.js:22:18)
        at Object.<anonymous> (/data/pulumi/node_modules/grpc/src/client_interceptors.js:144:12)
        at Module._compile (internal/modules/cjs/loader.js:689:30)
    (node:97) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)                                                                                                                 
    (node:97) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.                                                                                                                                                             

Resources:
    - 3 to delete
w
Was this something you saw only in the preview? Or did the update also go ahead and do the deletes after reporting this error? Both are problems, but the latter would be a very serious issue if you did see that happen.
b
I launched it with -y so it did go forward I believe, and yea even with -y I would think it should stop after that error
I can run another test for you, I'll try it a bit later
w
Opened https://github.com/pulumi/pulumi/issues/2316. If you do happen to be able to reproduce this or get more details, feel free to add them there.
b
ok i was able to reproduce it.. i’ll post some more info to the issue
posted 👍
Open in Slack
PreviousNext
Powered by