Actions
Bug #4229
closedconf parsing gives very confusing message if no '=' present on setting line
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
A doc bug caused a user to attempt to include settings of the form
public network <addr>
i.e. missing the equals sign. The config parsing ended up saying
"unexpected character while parsing putative key value, at char N line M", where N was "one past EOL".
The problematic code calls #, ;, and '\0' all "illegal characters in key names", which they are,
but, '\0' should probably be handled differently, issuing something like "no value found on line M; missing =?"
Actions