Actions
Bug #35847
closedwrong cluster_network doesn't cause any errors and ends up using monitor network?
Status:
Resolved
Priority:
High
Assignee:
Category:
Administration/Usability
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
1) set any random valid cluster network eg: cluster_network: 17.20.20.0/24
2) setup cluster , notice the cluster comes up and doesn't complain anything about wrong osd network
this is misleading to admin and should be fixed, since one believes that cluster network is in use
when it is not
I have tested this in octo lab in luminous, but believe this should exist in master as well, it is easy
to recreate with overrides in teuthology
Actions