:wave: i'm seeing a fun issue when adding a Servic...
# aws
b
👋 i'm seeing a fun issue when adding a ServiceRegistry to an ECS Service - please let me know if I should file this as a bug in /aws
Copy code
panic: fatal: An assertion has failed: Expected diff to not require deletion or replacement during Update of urn:pulumi:dev::sample-shared::fargate-nginx$aws:ecs/service:Service::sample-shar-app-service
    goroutine 1366 [running]:
    <http://github.com/pulumi/pulumi/sdk/v2/go/common/util/contract.failfast(...)|github.com/pulumi/pulumi/sdk/v2/go/common/util/contract.failfast(...)>
        /home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v2@v2.15.1-0.20201202214525-260620430c4c/go/common/util/contract/failfast.go:23
    <http://github.com/pulumi/pulumi/sdk/v2/go/common/util/contract.Assertf(0xc0020f7800|github.com/pulumi/pulumi/sdk/v2/go/common/util/contract.Assertf(0xc0020f7800>, 0x773aaa5, 0x48, 0xc002467778, 0x1, 0x1)
        /home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v2@v2.15.1-0.20201202214525-260620430c4c/go/common/util/contract/assert.go:33 +0x1a5
    <http://github.com/pulumi/pulumi-terraform-bridge/v2/pkg/tfbridge.(*Provider).Update(0xc00000a780|github.com/pulumi/pulumi-terraform-bridge/v2/pkg/tfbridge.(*Provider).Update(0xc00000a780>, 0x80e1260, 0xc00141b1d0, 0xc0018c3f00, 0xc00000a780, 0x688db01, 0xc001c36500)
        /home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v2@v2.15.3/pkg/tfbridge/provider.go:958 +0x831
    <http://github.com/pulumi/pulumi/sdk/v2/proto/go._ResourceProvider_Update_Handler.func1(0x80e1260|github.com/pulumi/pulumi/sdk/v2/proto/go._ResourceProvider_Update_Handler.func1(0x80e1260>, 0xc00141b1d0, 0x7443da0, 0xc0018c3f00, 0x7406e00, 0xc117940, 0x80e1260, 0xc00141b1d0)
        /home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v2@v2.15.1-0.20201202214525-260620430c4c/proto/go/provider.pb.go:2305 +0x8b
    <http://github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1(0x80e1260|github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1(0x80e1260>, 0xc001027980, 0x7443da0, 0xc0018c3f00, 0xc000a2eb80, 0xc000a2eba0, 0x0, 0x0, 0x8014560, 0xc00007e8d0)
        /home/runner/go/pkg/mod/github.com/grpc-ecosystem/grpc-opentracing@v0.0.0-20180507213350-8e809c8a8645/go/otgrpc/server.go:57 +0x2f6
    <http://github.com/pulumi/pulumi/sdk/v2/proto/go._ResourceProvider_Update_Handler(0x75046e0|github.com/pulumi/pulumi/sdk/v2/proto/go._ResourceProvider_Update_Handler(0x75046e0>, 0xc00000a780, 0x80e1260, 0xc001027980, 0xc00241dbc0, 0xc001564c20, 0x80e1260, 0xc001027980, 0xc001617800, 0xb6f)
        /home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v2@v2.15.1-0.20201202214525-260620430c4c/proto/go/provider.pb.go:2307 +0x150
    <http://google.golang.org/grpc.(*Server).processUnaryRPC(0xc000a87180|google.golang.org/grpc.(*Server).processUnaryRPC(0xc000a87180>, 0x81060e0, 0xc00034a180, 0xc0003b0400, 0xc001603b30, 0xc0d2ff8, 0x0, 0x0, 0x0)
        /home/runner/go/pkg/mod/google.golang.org/grpc@v1.30.0/server.go:1171 +0x522
    <http://google.golang.org/grpc.(*Server).handleStream(0xc000a87180|google.golang.org/grpc.(*Server).handleStream(0xc000a87180>, 0x81060e0, 0xc00034a180, 0xc0003b0400, 0x0)
        /home/runner/go/pkg/mod/google.golang.org/grpc@v1.30.0/server.go:1494 +0xcc5
    <http://google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc000368020|google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc000368020>, 0xc000a87180, 0x81060e0, 0xc00034a180, 0xc0003b0400)
        /home/runner/go/pkg/mod/google.golang.org/grpc@v1.30.0/server.go:834 +0xa5
    created by <http://google.golang.org/grpc.(*Server).serveStreams.func1|google.golang.org/grpc.(*Server).serveStreams.func1>
        /home/runner/go/pkg/mod/google.golang.org/grpc@v1.30.0/server.go:832 +0x1fd
using version:
"@pulumi/aws": "^3.20.0-alpha.1607448411",
just updated to v3.23.0
c
yes, can you please open a ticket here
Are you able to do a
pulumi destroy
and then add the ServiceRegistry arn that you need and do a
pulumi up
to see if the error goes away as a work around?
b
@cool-fireman-90027 yes, that worked - thank you!
c
Can we get the steps(including code) to reproduce the error added to 1297 issue?
b
certainly