udpating error message returned from getUserCredentials to avoid logs looping … #569
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…forever
This closes #
#551
Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed
Note to contributors: remember to re-generate client set if there are any API changes
Summary Of Changes
It seems like that when we delete a credential user secret the messaging operator prints continuously logs like:
ZI43wvWvLfxxFsWYdeykLxeKy4mWMX5}}] &LocalObjectReference{Name:myuser-2-user-credentials,} EZI43wvWvLfxxFsWYdeykLxeKy4mWMX5}}] &LocalObjectReference{Name:myuser-2-user-credentials,} EZI43wvWvLfxxFsWYdeykLxeKy4mWMX5}}] &LocalObjectReference{Name:myuser-2-user-credentials,} EZI43wvWvLfxxFsWYdeykLxeKy4mWMX5}}] &LocalObjectReference{Name:myuser-2-user-credentials,} EZI43wvWvLfxxFsWYdeykLxeKy4mWMX5}}] &LocalObjectReference{Name:myuser-2-user-credentials,} EZI43wvWvLfxxFsWYdeykLxeKy4mWMX5}}] &LocalObjectReference{Name:myuser-2-user-credentials,} EZI43wvWvLfxxFsWYdeykLxeKy4mWMX5}}] &LocalObjectReference{Name:myuser-2-user-credentials,} EZI43wvWvLfxxFsWYdeykLxeKy4mWMX5}}] &LocalObjectReference{Name:myuser-2-user-credentials,} EZI43wvWvLfxxFsWYdeykLxeKy4mWMX5}}] &LocalObjectReference{Name:myuser-2-user-credentials,}
and
2023-03-06T14:21:00Z ERROR Reconciler error {"controller": "user", "controllerGroup": "rabbitmq.com", "controllerKind": "User", "User": {"name":"myuser-2","namespace":"rabbitmq-system"}, "namespace": "rabbitmq-system", "name": "myuser-2", "reconcileID": "cd7a69ea-5e53-4e2f-9523-746062bd13bf", "error": "failed to retrieve user credentials secret from status; user.status: {1 [{Ready False 2023-03-06 14:20:41 +0000 UTC FailedCreateOrUpdate failed to retrieve user credentials secret from status; user.status: {1 [{Ready False 2023-03-06 14:20:41 +0000 UTC FailedCreateOrUpdate failed to retrieve user credentials secret from status; user.status: {1 [{Ready False 2023-03-06 14:20:41 +0000 UTC FailedCreateOrUpdate failed to retrieve user credentials secret from status; user.status: {1 [{Ready False 2023-03-06 14:20:41 +0000 UTC FailedCreateOrUpdate failed to retrieve user credentials secret from status; user.status: {1 [{Ready False 2023-03-06 14:20:41 +0000 UTC FailedCreateOrUpdate failed to retrieve user credentials secret from status; user.status: {1 [{Ready False 2023-03-06 14:20:41 +0000 UTC FailedCreateOrUpdate failed to retrieve user credentials secret from status; user.status: {1 [{Ready False 2023-03-06 14:20:41 +0000 UTC FailedCreateOrUpdate failed to retrieve user credentials secret from status; user.status: {1 [{Ready False 2023-03-06 14:20:41 +0000 UTC FailedCreateOrUpdate failed to retrieve user credentials secret from statu
This modification seems preventing this to happen. The error will be printed just at every reconciliation loop.
Additional Context