Bug #58132
qa/standalone/mon: --mon-initial-members setting causes us to populate removed_ranks
0%
Description
Problem:
--mon-initial-members does nothing but cause monmap
to populate ``removed_ranks`` because the way we start
monitors in standalone tests uses ``run_mon $dir $id ..``
on each mon. Regardless of --mon-initial-members=a,b,c, if
we set --mon-host=$MONA,$MONB,$MONC (which we do every single test),
every time we run a monitor (e.g.,run mon.b) it will pre-build
our monmap with
```
noname-a=mon.noname-a addrs v2:127.0.0.1:7127/0,
b=mon.b addrs v2:127.0.0.1:7128/0,
noname-c=mon.noname-c addrs v2:127.0.0.1:7129/0,
```
Now, with --mon-initial-members=a,b,c we are letting
monmap know that we should have initial members name:
a,b,c, which we only have `b` as a match. So what
``MonMap::set_initial_members`` do is that it will
remove noname-a and noname-c which will
populate `removed_ranks`.
Solution:
remove all instances of --mon-initial-members
in the standalone test as it has no impact on
the nature of the tests themselves.
Related issues
History
#1 Updated by Kamoltat (Junior) Sirivadhna about 1 year ago
- Pull request ID set to 48698
#2 Updated by Kamoltat (Junior) Sirivadhna about 1 year ago
- Status changed from New to In Progress
#3 Updated by Kamoltat (Junior) Sirivadhna about 1 year ago
- Pull request ID changed from 48698 to 48991
#4 Updated by Radoslaw Zarzynski 12 months ago
- Status changed from In Progress to Pending Backport
- Backport set to pacific,quincy
#5 Updated by Backport Bot 12 months ago
- Copied to Backport #58335: quincy: qa/standalone/mon: --mon-initial-members setting causes us to populate removed_ranks added
#6 Updated by Backport Bot 12 months ago
- Copied to Backport #58336: pacific: qa/standalone/mon: --mon-initial-members setting causes us to populate removed_ranks added
#7 Updated by Backport Bot 12 months ago
- Tags set to backport_processed
#8 Updated by Kamoltat (Junior) Sirivadhna 8 months ago
- Status changed from Pending Backport to Resolved
All backports are merged