my-rook-config

Files

T

Joshua Hoblitt 0763f91f93 operator: silence 'cm is handled by another watcher' DEBUG messages

I guesstimate that around 50% of the operator log volume when set to log
level `DEBUG` are messages about cm's which aren't relevant to rook.

E.g.:

```
2022-09-16 23:03:05.430839 D | ceph-cluster-controller: hot-plug cm watcher: only reconcile on hot plug cm changes, this "ingress-controller-leader" cm is handled by another watcher
2022-09-16 23:03:05.643255 D | ceph-cluster-controller: hot-plug cm watcher: only reconcile on hot plug cm changes, this "fleet-agent-lock" cm is handled by another watcher
2022-09-16 23:03:05.799526 D | ceph-cluster-controller: hot-plug cm watcher: only reconcile on hot plug cm changes, this "cattle-controllers" cm is handled by another watcher
```

Yes, it is `DEBUG` and noise is expected. However, there is no message
about checking the status of the cm's rook actually needs to watch and
these messages don't seem very useful. I have been resorting to piping
the operators logs through `| grep -v 'hot-plug cm watcher'` to cut down
the noise.

Signed-off-by: Joshua Hoblitt <josh@hoblitt.com>

2022-09-16 16:23:19 -07:00

apis/ceph.rook.io

Merge pull request #10950 from BlaineEXE/nfs-kerberos-implementation

2022-09-13 10:05:14 -06:00

client

build: format comments for go 1.19

2022-08-11 12:41:10 -06:00

clusterd

Merge pull request #10230 from leseb/fix-9470

2022-05-10 09:07:09 +09:00

daemon

Merge pull request #10968 from cybozu-go/osd-disallow-to-create-encrypted-osd-on-part