Environment
- Affects: YugabyteDB Anywhere (YBA Installer) 2.18.5, 2.20.0
- Fixed In: 2.18.6.0, 2.20.1.1
Issue
On a YBA Installer installation, where java_non_proxy
is used, an upgrade to an affected version fails with the following error:
The config at /opt/yba-ctl/yba-ctl.yml is not valid. Errors:- platform.proxy.java_non_proxy: Must validate at least one schema (anyOf)- platform.proxy.java_non_proxy: String length must be less than or equal to 0
Resolution
Overview
In the affected versions, a bug was introduced in the yba-installer-input-json-schema.json
template that defines the acceptable values for java_non_proxy
. Specifically, the bug unnecessarily restricts strings to a max length of zero characters.
The fix involves removing this max length restriction.
Steps
On the YBA node:
1. Edit file /opt/yugabyte/software/<target-version>/yba_installer/templates/yba-installer-input-json-schema.json
(as yugabyte user) and remove the "maxLength": 0
line from "java_non_proxy"
Before:
"java_non_proxy": {
"anyOf": [
{
"type": "string",
"maxLength": 0
},
{
"type": "integer"
}
After:
"java_non_proxy": {
"anyOf": [
{
"type": "string",
},
{
"type": "integer"
}
2. Re-run the upgrade
Comments
0 comments
Please sign in to leave a comment.