Closed pulumi-bot closed 1 month ago
There seems to be a permadiff on the Launch Configuration now that trips the empty update after create tests:
~ userData:
- 6b88c22b7239ed0661ed5d730b5fb2398c680015
+ #!/bin/bash
+ /etc/eks/bootstrap.sh --apiserver-endpoint "https://f86bdf6f859d5dda5b5ddbfa5f7992ed.gr7.us-west-2.eks.amazonaws.com/" --b64-cluster-ca "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURCVENDQWUyZ0F3SUJBZ0lJYXBTSis0cnVmYjR3RFFZSktvWklodmNOQVFFTEJRQXdGVEVUTUJFR0ExVUUKQXhNS2EzVmlaWEp1WlhSbGN6QWVGdzB5TkRBNU1Ea3dOelU0TVRWYUZ3MHpOREE1TURjd09EQXpNVFZhTUJVeApFekFSQmdOVkJBTVRDbXQxWW1WeWJtVjBaWE13Z2dFaU1BMEdDU3FHU0liM0RRRUJBUVVBQTRJQkR3QXdnZ0VLCkFvSUJBUURhQnpUUU0zclVlSUJmUENlQ3ZyUVhLM1lXNWlXVHI3eU9JMUovTFZxQlpKaEdzS0YzNDZBZStwajEKREdqYklIbHpVSXF4UmNYc2prdFA1TXZZMGRXMHZoelRtU3ZENk1pWGxCZENvTzFONXk3UUFQMHFoTmRBaktYeApsMGlMY1VxZkZHRjNqemFqNSszWGV3YTFqbTFqbjFzdm1VR1hpREpQUHppeG9YNWlOUjFQRUY4bTAxT1N4QTVuCmRYTHNkOEFRUGV6ekdkNUNUSDE0MTBhdjdWSjVaLzE1b3ZiZEsxeGZHc2ZjeU40Q2M4cnZFaXFWTDNSUWowT00KOWpiYzRZM0lMWFphVFdCbE9zUnlXd1FUSlMrVHlyOHFaVEVoRmdlc3lKR3RoU0EzZktWc3c4eTNRRDdrSUNNdgpodmRMUSt4UXcvVW5NNjlEU0FKTEhXWjRsclVOQWdNQkFBR2pXVEJYTUE0R0ExVWREd0VCL3dRRUF3SUNwREFQCkJnTlZIUk1CQWY4RUJUQURBUUgvTUIwR0ExVWREZ1FXQkJSVElqNjhI
N2dFTEZuaFl2MUR5SFMyRlZjalZEQVYKQmdOVkhSRUVEakFNZ2dwcmRXSmxjbTVsZEdWek1BMEdDU3FHU0liM0RRRUJDd1VBQTRJQkFRQXZqVnJDRkVzLwo1TkxUbENsNEJLeGhiWUZBVVlKN0hWN2VldEJISVBoZGFwQ21rcUc1RHU3RzZLeGtSOTJkREFCVHpoMFN2WWtQClVkZXFmQzZZc3BRbi8zTzRPaFQ4OE9iQ1cyYjJVdVc1d2s0cVNlaXhIREZXSTRlalZRYmIzbUhUY0UxUHlLUFoKL2t5N2lKdmNyNGVIMFNyTzdnanlacU1ONkV5ZWFNS3B2cTVOR3hqUG95ckltSlJJOEdpS21qN2ZlcGVnSW94NgpNOTBEZC9JNkNxaVZqNnNoV1ZJS3J5VTJTSGEvR2lib2tJS0kxa0JvaU9CdFRsMmhGeHlYVjYvajhHYU1pU2lLCkVQaFBpWmEzUXVONzNMd1lXY1RDUHozZTBwbnhnS3Avd3RIaWVqRXJvMytBS3ZSQ0EvV1MxWnJOZlRVN1ZpaU8KUWxuQWplMXlUQ1pUCi0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K" "example-aws-profile-eksCluster-e41d30b"
I'm not yet sure what introduced this, we haven't changed this code in a long time. Will need to debug this locally, not enough information in the test output
The userdata in olds and news seems to be identical.
But what's interesting though is that it seems to compare 6b88c22b7239ed0661ed5d730b5fb2398c680015
(which is the SHA1 of the userdata) with the actual string contents.
The tests that are failing are ones that provide a custom AWS provider. They're using the latest provider ("version":"6.51.0"
).
Incidentally this is the one where PRC was rolled out. I'm gonna try to see if using an older provider works.
This is caused by a regression in AWS 6.51.0
: https://github.com/pulumi/pulumi-aws/issues/4446
This is fixed now tests are passing again.
Workflow Failure
cron has failed. See the list of failures below:
2024-09-07T07:45:20.000Z
2024-09-08T07:40:52.000Z
2024-09-09T07:49:18.000Z
2024-09-09T08:42:46.000Z
2024-09-10T07:42:45.000Z
2024-09-11T07:43:11.000Z