DBAAS MySQL and Opensearch continuously send updates to Exoscale

[gilberts42]

Description

The DBAAS MySQL and Opensearch continuously send an "Update" to Exoscale (this means every 1-2 minutes). This behaviour does not happen for DBAAS PostgreSQL. It can be observed through the Audit-Log in the Exoscale-UI:

It looks like the "observe" sees a difference while actually no difference exists.

Additional Context

No response

Logs

No INFO level logs are visible (neither for real change, nor for "no change").

2024-07-09T14:15:19.794Z | INFO | provider-exoscale.operator | pipelineutil/log.go:15 | Entering step "fetch provider config" | {"controller": "opensearch", "controllerGroup": "exoscale.crossplane.io", "controllerKind": "OpenSearch", "OpenSearch": {"name":"gs-opensearch-test2"}, "namespace": "", "name": "gs-opensearch-test2", "reconcileID": "cb5f26d8-6e49-45c3-8f54-1b47b56febc2"}
2024-07-09T14:15:19.795Z | INFO | provider-exoscale.operator | pipelineutil/log.go:15 | Entering step "fetch secret" | {"controller": "opensearch", "controllerGroup": "exoscale.crossplane.io", "controllerKind": "OpenSearch", "OpenSearch": {"name":"gs-opensearch-test2"}, "namespace": "", "name": "gs-opensearch-test2", "reconcileID": "cb5f26d8-6e49-45c3-8f54-1b47b56febc2"}
2024-07-09T14:15:19.795Z | INFO | provider-exoscale.operator | pipelineutil/log.go:15 | Entering step "validate secret" | {"controller": "opensearch", "controllerGroup": "exoscale.crossplane.io", "controllerKind": "OpenSearch", "OpenSearch": {"name":"gs-opensearch-test2"}, "namespace": "", "name": "gs-opensearch-test2", "reconcileID": "cb5f26d8-6e49-45c3-8f54-1b47b56febc2"}
2024-07-09T14:15:19.795Z | INFO | provider-exoscale.operator | pipelineutil/log.go:15 | Entering step "create exoscale client" | {"controller": "opensearch", "controllerGroup": "exoscale.crossplane.io", "controllerKind": "OpenSearch", "OpenSearch": {"name":"gs-opensearch-test2"}, "namespace": "", "name": "gs-opensearch-test2", "reconcileID": "cb5f26d8-6e49-45c3-8f54-1b47b56febc2"}

Expected Behavior

Update should occur only whan a real change to the managed resources happen.

Steps To Reproduce

Create a MySQL or Openssearch DBAAS (with or without custom settings). Observe the Audit-Log in the Exoscale-UI.

Versions

xpkg.upbound.io/vshn/provider-exoscale:v0.11.1

[gilberts42]

Sincd 1st march we have the same problem in very high frequence, also for PostgresQL. It looks like since the change on Exoscale side, to not return secrets anymore from 1.3.2025 on, the detection of changes does not work correctly anymore.

It looks like this parameter is now expected to be set for postgresql: "password_encryption:md5", while setting it actually does not change anything and the same difference is detected in the next reconciliation loop again.

Additionally, logging here always "false" looks like a bug, logging the key and even better the exact difference which is detected would be very helpful:

provider-exoscale/operator/postgresqlcontroller/observe.go

Line 172 in bcc1a1b

log.V(2).Info("instance not up-to-date", "check", v)

[Kidswiss]

Hi @gilberts42

I've checked the audit log of one of our accounts and it looks like we had that issue even before the 1st of March for all services.

I'm opening an internal ticket so we can have a look at this.