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

PostReconcileCheck not running on BackupVaultBackupInstance resource #4135

Open
mayankagg9722 opened this issue Jun 25, 2024 · 5 comments
Open
Assignees
Labels
bug 🪲 Something isn't working
Milestone

Comments

@mayankagg9722
Copy link
Member

Version

ASO v2.7.0

Describe the bug
Seeing a regressed behavior where there is no post reconciliation and BeginSyncBackupInstance called on the BackupVaultsBackupInstance even though it was failed user error and in protection error state (our condition in post reconciliation)

https://github.com/mayankagg9722/azure-service-operator/blob/e66c3fd05fc6af0a4efb0551b858d01eee2c7376/v2/api/dataprotection/customizations/backup_vaults_backup_instance_extensions.go#L98

To Reproduce
Post performing all the prerequisutes, create the BackupVaultBackupInstance resource in the cluster using ASO.
Use this Yaml:
bie2etest.txt

Expected behavior
BeginSyncBackupInstance should be called which is there in the reconciliation flow.

https://github.com/mayankagg9722/azure-service-operator/blob/e66c3fd05fc6af0a4efb0551b858d01eee2c7376/v2/api/dataprotection/customizations/backup_vaults_backup_instance_extensions.go#L98

Screenshots
Activity logs portal:

image

Backup Instance:

image
image

ASO Logs:
image

asologs.txt
asologs1.txt

Backup Instance YAML in Cluster:

image

@mayankagg9722 mayankagg9722 added the bug 🪲 Something isn't working label Jun 25, 2024
@mayankagg9722
Copy link
Member Author

@theunrepentantgeek @super-harsh Please help me to debug this further.

@matthchr
Copy link
Member

matthchr commented Jul 1, 2024

We'll take a look at this

@mayankagg9722
Copy link
Member Author

I have discussed this with @super-harsh and he figured out that this commit by him caused this breaking change:
https://github.com/Azure/azure-service-operator/pull/3953/files.

We need to revert this checkin.

@matthchr
Copy link
Member

matthchr commented Jul 8, 2024

It sounds like @super-harsh and @mayankagg9722 synced up and figured out what the issue was, and Mayank will send a PR to help resolve it.

@theunrepentantgeek
Copy link
Member

We need to revert this checkin.

It's not as simple at this. We need to fix the regression, while keeping the quality-of-life improvements @super-harsh brought in. We also need to ascertain why the existing test suite didn't catch this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🪲 Something isn't working
Projects
Development

No branches or pull requests

4 participants