Description of problem: The logs in the CLO are chatty and don't provide more then noise where state can be reflected in CR status.
Moving to UpcomingSprint awaiting for PRs to merge, etc.
Moving to 4.7 to satisfy CF requirements for 4.6
Marking UpcomingSprint as will not be merged or addressed by EOD
Verified this on clusterlogging.4.7.0-202011021919.p0, elasticsearch-operator.4.7.0-202011030448.p0 and cluster 4.7.0-0.nightly-2020-10-27-051128. Not seeing state related logs in CLO.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Errata Advisory for Openshift Logging 5.0.0), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:0652