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

MySQLServer does not report errors that occur in the later stages of patch operation #84

Open
muvaf opened this issue Dec 25, 2019 · 0 comments · May be fixed by #88
Open

MySQLServer does not report errors that occur in the later stages of patch operation #84

muvaf opened this issue Dec 25, 2019 · 0 comments · May be fixed by #88
Assignees
Labels
bug Something isn't working

Comments

@muvaf
Copy link
Member

muvaf commented Dec 25, 2019

What happened?

I created a MySQLServer resource with the following SKU:

tier: Basic
capacity: 1
family: Gen5

Then I wanted to update it to the following:

tier: GeneralPurpose
capacity: 2
family: Gen5

I always see InProgress in lastOperation section of status but the polling URL keeps changing. Then I logged into Azure portal and saw a bunch of patch requests with error saying something like tier cannot be changed from Basic. But I didn't see that error in status of MySQLServer resource.

How can we reproduce it?

Create a MySQLServer resource with Basic tier and after creation, try to change that value to GeneralPurpose.

When I debugged the controller, I saw that the Azure server does not return an error in the first fetch async op call. So, it happens after a while. Then in the next reconcile, it fetches the operation and error comes in. However, before having a chance to update status, Update is triggered again since the status of the last operation is not InProgress anymore. Then we start over. That's why the polling URL keeps changing because each time a new Update is triggered but the error is not reported in-between Updates.

What environment did it happen in?

Crossplane version: 0.6.0
Azure Stack version: 0.4.0

@muvaf muvaf added the bug Something isn't working label Dec 25, 2019
@muvaf muvaf self-assigned this Jan 2, 2020
@muvaf muvaf linked a pull request Jan 2, 2020 that will close this issue
4 tasks
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
None yet
Development

Successfully merging a pull request may close this issue.

1 participant