Project

General

Profile

Actions

Bug #58132

closed

qa/standalone/mon: --mon-initial-members setting causes us to populate removed_ranks

Added by Kamoltat (Junior) Sirivadhna over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Category:
-
Target version:
-
% Done:

0%

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

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 2 (0 open2 closed)

Copied to RADOS - Backport #58335: quincy: qa/standalone/mon: --mon-initial-members setting causes us to populate removed_ranksResolvedKamoltat (Junior) SirivadhnaActions
Copied to RADOS - Backport #58336: pacific: qa/standalone/mon: --mon-initial-members setting causes us to populate removed_ranksResolvedKamoltat (Junior) SirivadhnaActions
Actions

Also available in: Atom PDF