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

Bug: SQL User error on GetDB in transitional state #905

Closed
frodopwns opened this issue Apr 9, 2020 · 0 comments · Fixed by #928
Closed

Bug: SQL User error on GetDB in transitional state #905

frodopwns opened this issue Apr 9, 2020 · 0 comments · Fixed by #928
Assignees
Labels
bug 🪲 Something isn't working high-priority Issues we intend to prioritize (security, outage, blocking bug)

Comments

@frodopwns
Copy link
Contributor

Describe the bug
If you deploy a RG, SQLServer, SQLDatabase, SQLFirewall, SQLUser at the same time you will see uncaught errors in the SQL User (and SQL Db) operator.

2020-04-08T18:30:21.485-0600	ERROR	controller-runtime.controller	Reconciler error	{"controller": "azuresqluser", "request": "default/sqluser1", "error": "1 error occurred:\n\t* sql.DatabasesClient#Get: Failure responding to request: StatusCode=404 -- Original Error: json: cannot unmarshal array into Go struct field serviceError2.details of type map[string]interface {}\n\n"}

To Reproduce
put the manifests in a directory and run kubectl create -f <directory>...you won't see the errors until just before everything finishes...

everything comes up eventually but these errors should still be caught

Expected behavior
no stack traces in logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🪲 Something isn't working high-priority Issues we intend to prioritize (security, outage, blocking bug)
Projects
None yet
3 participants