fix: empty tenant log

[jiuker]

When update failed, tenant will reset to the default one without any information

minio-operator-bdb6b4f55-bkdg7 operator E0909 07:20:34.734171       1 main-controller.go:1570] error syncing '/': resource name may not be empty
minio-operator-bdb6b4f55-bkdg7 operator E0909 07:21:34.735160       1 main-controller.go:1570] error syncing '/': resource name may not be empty
minio-operator-bdb6b4f55-bkdg7 operator E0909 07:22:34.736224       1 main-controller.go:1570] error syncing '/': resource name may not be empty
minio-operator-bdb6b4f55-bkdg7 operator E0909 07:23:34.737242       1 main-controller.go:1570] error syncing '/': resource name may not be empty
minio-operator-bdb6b4f55-bkdg7 operator E0909 07:24:34.737571       1 main-controller.go:1570] error syncing '/': resource name may not be empty

[ramondeklein]

LGTM, but what could be the reason of updating pool status to fail?

[jiuker]

LGTM, but what could be the reason of updating pool status to fail?

Update conflicts

[ramondeklein]

Wouldn't skipping this result in an improper status? Shouldn't we retry determining the status if it hits a conflict?

But this PR is better than before, so let's merge it anyway...

[jiuker]

Wouldn't skipping this result in an improper status? Shouldn't we retry determining the status if it hits a conflict?

But this PR is better than before, so let's merge it anyway...

Yes, the tenant will be empty here, and the outermost layer will pass the tenant to the syncHandler for further processing