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

[v14] external audit storage results in NoncurrentVersionExpiration action must be a positive integer #48155

Closed
programmerq opened this issue Oct 30, 2024 · 4 comments
Assignees
Labels
aws Used for AWS Related Issues. bug

Comments

@programmerq
Copy link
Contributor

When running teleport integration configure externalauditstorage --bootstrap ... command to enable external audit storage, it fails with the following error:

ERROR: setting lifecycle configuration on S3 bucket 
    operation error S3: PutBucketLifecycleConfiguration, https response error StatusCode: 400, RequestID: aaa, HostID: bbb, api error InvalidArgument: 'NewerNoncurrentVersions' for NoncurrentVersionExpiration action must be a positive integer

It looks like this some issue was originally introduced on branch/v15 before 15.0.0, but was fixed by #37068.

It wasn't backported to branch/v14 at that time, but the same bug was later introduced in #39490.

It looks like backporting #37068 would be sufficient to fix it for branch/v14 too.

@programmerq programmerq added aws Used for AWS Related Issues. bug labels Oct 30, 2024
@rosstimothy
Copy link
Contributor

rosstimothy commented Oct 30, 2024

@nklaassen any reason branch/v14 did not get the backport?

@programmerq even if we get the backport in today, v14 is going to be EOL in a few weeks and might not receive another release.

@nklaassen
Copy link
Contributor

@rosstimothy the bug was introduced in v15 by a dependency update, v14 was still on the older version of aws-sdk-go-v2 and the fix wasn't relevant or even possible, this was an int vs *int issue with the update. marco later updated the depency in v14 but missed the fix

@rosstimothy
Copy link
Contributor

@nklaassen would you mind opening a backport then?

@nklaassen
Copy link
Contributor

sure, backport is up here #48179

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws Used for AWS Related Issues. bug
Projects
None yet
Development

No branches or pull requests

3 participants