rancher: [BUG] in Rancher Logging, Tests are not indicative of whether the config will work or not
What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):
- Select ES as target for cluster logging
- Use
Edit as Filemode and input the correct config - Click
Dry Run
Result: Dry run fails. Even the config is correct.
Environment information
- Rancher: v2.3.5
Tested on: Rancher Launched (Provider) EC2 cluster
- Kubernetes: v1.17.2
- Elasticsearch: standalone docker container elasticsearch:7.6.0
- Logging: v0.1.4
Rancher Launched (Provider) Google GKE cluster
- Kubernetes: v1.15.9-gke.24
- Elasticsearch: standalone docker container elasticsearch:7.6.0
- Logging: v0.1.4
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (16 by maintainers)
Commits related to this issue
- Update default fluentd configure to avoid deprecated configure warning Problem: Fluentd-tester which use this default configure, when click dry-run in the UI will get deprecated configure warning So... — committed to aiwantaozi/fluentd by aiwantaozi 4 years ago
- Update default fluentd configure to avoid deprecated configure warning Problem: Fluentd-tester which use this default configure, when click dry-run in the UI will get deprecated configure warning So... — committed to aiwantaozi/fluentd by aiwantaozi 4 years ago
- Fix logging dry-run function return error Problem: 1. Dry run return couldn't find pod fluentd-test because after refactor some controllers to agent, now we couldn't get pod from controller. 2. After... — committed to aiwantaozi/rancher by aiwantaozi 4 years ago
@cbron we can revert the charts PR to quick fix the duplicated configuration, fix in rancher is enough to fix the current problem, update fluentd configure isn’t necessary. I will update the fluentd configure, then we can release a new fluentd, then update the chart with next fluentd version.