Bug #48623
mgr/dashboard: Dashboard logs e2e tests are failing
Status:
Resolved
Priority:
High
Assignee:
Category:
dashboard/general
Target version:
% Done:
0%
Source:
Tags:
Backport:
nautilus, octopus
Regression:
No
Severity:
3 - minor
Description
Yesterday there were some changes went in which disables the logging of config set and config-key set to to be logged in mgr audit logs. Dashboard has an e2e test which checks for this config set and broke the current e2e jenkins job
Failure report:
1) Logs page
audit logs respond to editing configuration setting test
should change config settings and check audit logs reacted:
Timed out retrying
+ expected - actual
-'from=\'mgr.4139 \' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "client", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 172.21.2.17:0/31644\' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "client", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 \' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "mds", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 172.21.2.17:0/31644\' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "mds", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 \' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "osd", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 172.21.2.17:0/31644\' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "osd", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 \' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "mgr", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 172.21.2.17:0/31644\' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "mgr", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 \' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "mon", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 172.21.2.17:0/31644\' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "mon", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 \' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "client", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 172.21.2.17:0/31644\' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "client", "name": "log_graylog_port"}]: dispatchfrom=\'mgr.4139 \' entity=\'mgr.x\' cmd=[{"prefix": "config rm", "format": "json", "who": "mds", "name": "log_graylog_port"}]: dispatch'
+'global'
at LogsPageHelper.checkAuditForConfigChange (https://braggi17:41869/__cypress/tests?p=cypress/integration/cluster/logs.e2e-spec.ts:309:14)
at Context.eval (https://braggi17:41869/__cypress/tests?p=cypress/integration/cluster/logs.e2e-spec.ts:233:18)
Related issues
History
#1 Updated by Nizamudeen A about 1 month ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 38606
#2 Updated by Nizamudeen A about 1 month ago
- Description updated (diff)
#3 Updated by Ernesto Puerta about 1 month ago
- Status changed from Fix Under Review to Resolved
#4 Updated by Ernesto Puerta about 1 month ago
- Status changed from Resolved to Pending Backport
- Backport set to nautilus, octopus
#5 Updated by Ernesto Puerta about 1 month ago
- Blocked by Bug #37503: Audit log: mgr module passwords set on CLI written as plaintext in log files added
#6 Updated by Backport Bot about 1 month ago
- Copied to Backport #48625: nautilus: mgr/dashboard: Dashboard logs e2e tests are failing added
#7 Updated by Backport Bot about 1 month ago
- Copied to Backport #48626: octopus: mgr/dashboard: Dashboard logs e2e tests are failing added
#8 Updated by Nizamudeen A 15 days ago
- Backport changed from nautilus, octopus to octopus
#9 Updated by Nathan Cutler 12 days ago
- Backport changed from octopus to nautilus, octopus
Reverting the previous change to prevent the "backport-create-issue" script from complaining like this:
ERROR:root:https://tracker.ceph.com/issues/48623 has more backport issues (nautilus,octopus) than expected (octopus)
#10 Updated by Nathan Cutler 12 days ago
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
#11 Updated by Nizamudeen A 8 days ago
- Status changed from Pending Backport to Resolved