Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If provisioner fails changeset is stuck preparing #4750

Closed
matt2e opened this issue Mar 3, 2025 · 0 comments · Fixed by #4761
Closed

If provisioner fails changeset is stuck preparing #4750

matt2e opened this issue Mar 3, 2025 · 0 comments · Fixed by #4761
Assignees

Comments

@matt2e
Copy link
Collaborator

matt2e commented Mar 3, 2025

Steps to repro:

  • Break the code in dev_provisioner.go:125 so that provisioning postgres always fails
func provisionPostgres(postgresPort int, recreate bool) InMemResourceProvisionerFn {
	return func(ctx context.Context, changeset key.Changeset, deployment key.Deployment, resource schema.Provisioned) (*schema.RuntimeElement, error) {
		time.Sleep(3 * time.Second)
		return nil, fmt.Errorf("not implemented")
  • ftl dev examples/go

Expected:

  • changeset should fail and postgres module should show a failure to build
info:types:build: Module built (4.69s)
info:mysql:build: Module built (1.92s)
info:cron: API server listening at: 127.0.0.1:64246
info:schemaservice: Rolling back changeset chs-q5n0w8on0v0ijir: error running deployments: error running deployment: error running task postgres: error provisioning resources: provisioning failed: not implemented
info:pubsub: API server listening at: 127.0.0.1:64275
info:types: API server listening at: 127.0.0.1:64323
info:mysql: API server listening at: 127.0.0.1:64351
info:cron: Frequent cron job triggered.
> changeset list
chs-q5n0w8on0v0ijir	State: CHANGESET_STATE_PREPARING	Modules: [postgres]	Removing []
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants