Skip to content

Conversation

@OriolMunoz-da
Copy link
Contributor

Signed-off-by: Oriol Muñoz <oriol.munoz@digitalasset.com>
Signed-off-by: Oriol Muñoz <oriol.munoz@digitalasset.com>
break
else
(( i++ ))&& (( i > 300 )) &&_error "Timed out waiting for backup of $description db"
(( i++ ))&& (( i > WAIT_FOR_BACKUP_RETRIES )) && {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did this time out too?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, but I'd rather mirror the behavior between both

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the consistency but sentences that contain both delete and backup always make scared and look more closely...

else
(( i++ )) && (( i > 300 )) && _error "Timed out waiting for backup of $description PVC"
(( i++ )) && (( i > WAIT_FOR_BACKUP_RETRIES )) && {
kubectl delete volumesnapshot -n "$namespace" "$backupName";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we know we're allowed to delete here at all? If an operation is running then this will just fail too, won't it? But I guess that's fine because then we'll still retry?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

then we'll still retry

Hm or will this script just die, because we're not capturing the error code of the kubectl delete?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hopefully it works and it gets deleted, but otherwise you're correct, it will exit 1 and retry

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm and assuming the delete never works... will we loop forever here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

_error has an exit 1 inside, so either kubectl delete fails or _error exits

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it does... so fine then, not veto-ing if you feel confident about this.

Copy link
Contributor

@martinflorian-da martinflorian-da left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

WDYT about trying it without the deletes first? Not sure how much we're gaining for the risks here (of this not working as expected, of this deleting some other backup accidentally (low risk, I know))

Signed-off-by: Oriol Muñoz <oriol.munoz@digitalasset.com>
@OriolMunoz-da OriolMunoz-da enabled auto-merge (squash) January 23, 2026 10:04
@OriolMunoz-da OriolMunoz-da merged commit 925dcf9 into main Jan 23, 2026
44 checks passed
@OriolMunoz-da OriolMunoz-da deleted the oriol/reset-backup-timeouts branch January 23, 2026 10:12
isegall-da added a commit that referenced this pull request Jan 23, 2026
…e-backup (#3662)"

This reverts commit 925dcf9.

Signed-off-by: Itai Segall <itai.segall@digitalasset.com>
isegall-da added a commit that referenced this pull request Jan 23, 2026
…e-backup (#3662)" (#3674)

This reverts commit 925dcf9.

Signed-off-by: Itai Segall <itai.segall@digitalasset.com>
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 this pull request may close these issues.

3 participants