keystone_bootstrap.sh fails to display error message due to unprintable characters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
Medium
|
Unassigned | ||
Rocky |
Fix Released
|
Medium
|
Mark Goddard | ||
Stein |
Fix Released
|
Medium
|
Mark Goddard | ||
Train |
Fix Released
|
Medium
|
Mark Goddard | ||
Ussuri |
Fix Released
|
Medium
|
Unassigned |
Bug Description
First discussed in https:/
In some situations, Keystone bootstrap can fail, and then unhelpfully fails displaying the error message output by the 'keystone-manage bootstrap' command. This appears to be due to unprintable control characters in the error message which prevent the output of the script from being valid JSON.
Reproducing some of Rowan's investigation here. He ran the command manually, and captured the output in file.txt.
"
$ cat -vE file.txt
{"failed": true, "msg": "2019-11-25 12:57:43.952 541 WARNING keystone.
I believe the ^[[00m in the "msg" field is causing the issue. If I pipe the response to jq I receive similar errors:
parse error: Invalid string: control characters from U+0000 through U+001F must be escaped at line 1, column 342
"
Note that this issue is simply about the error display, not the underlying issue.
Changed in kolla-ansible: | |
importance: | Undecided → Medium |
milestone: | none → 10.0.0 |
Fix proposed here: https:/ /review. opendev. org/#/c/ 697982