Description of problem:
Deploy logging with no ops cluster and based on 3.6 or an earlier 3.7 pre-release which does not have the @OUTPUT label in fluent.conf
update to a recent fluentd image
no operations logs are stored
Version-Release number of selected component (if applicable):
Steps to Reproduce:
With logging-fluentd/images/v3.7.7-1. The .operations logs can be found both mux is enabled and disabled when OUPPUT label is removed. I think the test result is pass.
The bug is move from ON_QA to Modified, Is there other fix?
(In reply to Anping Li from comment #3)
> With logging-fluentd/images/v3.7.7-1. The .operations logs can be found both
> mux is enabled and disabled when OUPPUT label is removed. I think the test
> result is pass.
> The bug is move from ON_QA to Modified, Is there other fix?
Did you deploy without OPS cluster? The bug can only be reproduced when you deploy logging without OPS cluster. If you did not deploy OPS cluster, and you could not reproduce the issue, then the bug is verified.
Yes, I had Deployed without OPS cluster. so move to verified.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.