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

aws-redshift-alpha: getting 'A previous rotation isn't complete. That rotation will be reattempted' #28539

Closed
omer727 opened this issue Dec 31, 2023 · 2 comments
Labels
@aws-cdk/aws-redshift Related to Amazon Redshift bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. effort/medium Medium work item – several days of effort p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.

Comments

@omer727
Copy link

omer727 commented Dec 31, 2023

Describe the bug

When upgrade from 2.93.0-alpha.0 to 2.117.0-alpha.0 I'm getting:
'A previous rotation isn't complete. That rotation will be reattempted'
while doing deployment.

Expected Behavior

deployed successfully

Current Behavior

deployment is failing with a message 'A previous rotation isn't complete. That rotation will be reattempted'

Reproduction Steps

create a stack with the following info

this.redshiftCluster = new Cluster(this, 'redshift', {
            clusterType: props.stage === 'main' ? ClusterType.MULTI_NODE : ClusterType.SINGLE_NODE,
            defaultDatabaseName: databaseName,
            encrypted: true,
            // loggingBucket: bucket, //todo
            // loggingKeyPrefix: `${props.serviceName}-${props.stage}`,
            masterUser: {
                masterUsername: this.redshiftUserName,
            },
            nodeType: NodeType.DC2_LARGE,
            numberOfNodes: props.stage === 'main' ? 2 : 1,
            port,
            removalPolicy: props.stage === 'main' ? RemovalPolicy.RETAIN : RemovalPolicy.DESTROY,
            roles: roles,
            securityGroups: [sg],
            vpc,
            vpcSubnets: { subnets: [vpc.publicSubnets[0]] },
            preferredMaintenanceWindow: 'Sun:01:00-Sun:10:00',
            clusterName: this.clusterIdentifier,
        });

        this.redshiftCluster.addRotationSingleUser();

on 2.117.0-alpha.0 you'll get the error message

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.117

Framework Version

No response

Node.js Version

node 20

OS

mac

Language

TypeScript

Language Version

5.2.2

Other information

No response

@omer727 omer727 added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Dec 31, 2023
@github-actions github-actions bot added the @aws-cdk/aws-redshift Related to Amazon Redshift label Dec 31, 2023
@pahud
Copy link
Contributor

pahud commented Jan 2, 2024

Probably related to #17265

Did you see any timeout logs in the rotation lambda log?

@pahud pahud added p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. effort/medium Medium work item – several days of effort and removed needs-triage This issue or PR still needs to be triaged. labels Jan 2, 2024
Copy link

github-actions bot commented Jan 4, 2024

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Jan 4, 2024
@github-actions github-actions bot closed this as completed Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-redshift Related to Amazon Redshift bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. effort/medium Medium work item – several days of effort p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Projects
None yet
Development

No branches or pull requests

2 participants