Project

General

Profile

Actions

Bug #44188

closed

Module 'cephadm' has failed: dictionary changed size during iteration

Added by Sage Weil about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

2020-02-18T21:20:49.750+0000 7fc167767700  0 [cephadm] [DEBUG] [root]  host mira099 ok
2020-02-18T21:20:49.750+0000 7fc167767700  0 [cephadm] [DEBUG] [root]  checking mira116

...
2020-02-18T21:20:49.838+0000 7fc15bce8700  1 -- [v2:172.21.2.203:6896/1,v1:172.21.2.203:6897/1] <== client.733469116 172.21.6.108:0/931374390 1 ==== mgr_command(tid 0: {"prefix": "orch host rm", "host": "mira070", "target": ["mon-mg
2020-02-18T21:20:49.838+0000 7fc15bce8700 10 mgr.server _handle_command decoded-size=3 prefix=orch host rm
2020-02-18T21:20:49.838+0000 7fc15bce8700 20 is_capable service=py module=orchestrator_cli command=orch host rm read write addr - on cap allow *
2020-02-18T21:20:49.838+0000 7fc15bce8700 20  allow so far , doing grant allow *
2020-02-18T21:20:49.838+0000 7fc15bce8700 20  allow all
2020-02-18T21:20:49.838+0000 7fc15bce8700 10 mgr.server _allowed_command  client.admin capable
2020-02-18T21:20:49.838+0000 7fc15bce8700  0 log_channel(audit) log [DBG] : from='client.733469116 -' entity='client.admin' cmd=[{"prefix": "orch host rm", "host": "mira070", "target": ["mon-mgr", ""]}]: dispatch
2020-02-18T21:20:49.838+0000 7fc15bce8700 10 mgr.server _handle_command passing through 3
...
2020-02-18T21:20:50.146+0000 7fc167767700  0 [cephadm] [DEBUG] [root]  host mira116 ok
2020-02-18T21:20:50.146+0000 7fc167767700 -1 log_channel(cluster) log [ERR] : Unhandled exception from module 'cephadm' while running on mgr.reesi003: dictionary changed size during iteration
Actions #1

Updated by Sebastian Wagner about 4 years ago

  • Priority changed from Urgent to Immediate
Actions #2

Updated by Sebastian Wagner about 4 years ago

  • Priority changed from Immediate to Urgent

yes, deployed without issue, but again only one monitor was deployed. And when I tried to add other monitors this error happend.

Actions #3

Updated by Sage Weil about 4 years ago

  • Status changed from New to Resolved
  • Pull request ID set to 33359
Actions

Also available in: Atom PDF