Hey folks! Recently after upgrading my local Go ve...
# golang
g
Hey folks! Recently after upgrading my local Go version to 1.26, I've been having trouble with CI (Github Actions) and Pulumi. The situation I'm seeing is that CI will run the preview command. It will fail on the Pulumi side, but I can't find the reason and CI will just hang forever. I then tried updating all of my dependencies in all of the Pulumi Go modules. It seemed to have worked, And I was working on my dev stack for a while, but now I tried to tag a release which deploys to prod and the same thing happens. Has anyone encountered something similar? I tried searching the channel a little bit and all I could find was something about updating dependencies which I have, so I'm not really sure...
A weird thing I'm seeing is that the top status shows the update as succeeded, but then the preview is failed, and CI just hangs on "compiling".
Copy code
Infrastructure Deploy
  Logging in using access token from PULUMI_ACCESS_TOKEN
  Previewing update (prod)
  View Live: <https://app.pulumi.com/altys/altys-app/prod/previews/xxx>.....
  Downloading plugin gcp-9.17.0: starting
  Downloading plugin gcp-9.17.0: done
  Installing plugin gcp-9.17.0: starting
  @ Previewing update....
  Installing plugin gcp-9.17.0: done
      pulumi:pulumi:Stack altys-app-prod  Compiling the program ...
I retried the GHA job and it succeeded, so something is flaky, I'd love to find the root cause here.
s
Hmm that's an odd one! Does it work consistently after the first success or does the issue keep popping up occasionally?
g
I can't give you a concrete answer. It was happening very frequently on the dev stack, and then I suspected that the issue was upgrading Go, So I went and updated all of my Pulumi dependencies in go.mod and The version declaration itself in that file, And since then I've not had issues with the dev stack, but the first time I tried the prod stack (Same code, same dependencies, same versions, just a different YAML) it happened again. Retrying fixed it, but I didn't try to deploy it to prod since. We only do that once every few days. The thing that is consistently happening is that when I do see this issue on the Pulumi side, GitHub Actions will hang.
s
Hmm it could be a caching issue or it's getting stuck downloading dependencies the first time if there's a large set. Does the Pulumi console show a specific error in the Summary or Diagnostic tabs?
g
nothing
s
Thanks for sharing! I'll ask around a bit to see if anyone knows what the root cause could be. Please let me know if it starts failing again too!
g
btw Neo is also not helpful in that situation, it claims there's no failing update. It seems like it can't find the current one that's failing and telling me that the previous one succeeded. (At this point I'm just showing you links from a few days ago because now we are all green on all stacks)
e.g. when 200 was failing:
It's a little bit of a weird UX because I'm clicking a button to analyze a problem on number 200 and then NEO says 200 doesn't exist. Like it's gaslighting me 😄
If your team needs IDs for any entity, I can share everything.
s
Yea, that's strange! If you try pointing out that it's a preview, can Neo find it? If you've got IDs for the Neo task and update, that'd definitely help! Feel free to DM me if you don't want to share in the public channel
g
Cool, thanks. Yeah I'll DM some links.
🙏 1