upgrade to 2.3.6 failed: the dotted field is not valid for storage
Bug #1765722 reported by
Doug Parrish
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
John A Meinel | ||
2.3 |
Fix Released
|
Critical
|
John A Meinel |
Bug Description
upgrade-juju of controller model, from 2.3.5 to 2.3.6 fails. From controller model machine-0's log:
2018-04-19 22:49:15 ERROR juju.worker.
MongoDB apparently doesn't like keys with dots.
tags: | added: sts |
tags: | added: docteam |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 2.3.7 |
Changed in juju: | |
assignee: | nobody → John A Meinel (jameinel) |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Here is a reproducer:
~ $ juju bootstrap --bootstrap-series xenial --agent-version 2.3.5 lxd lxd /github. com/lxc/ lxd/blob/ master/ doc/production- setup.md localhost. .. cluster- 261". cluster- 261". kVpxxY2CBKS7mWF sSsLdKGzb5 kVpxxY2CBKS7mWF sSsLdKGzb5 GWMt9zrHt2psNKz BX2ykc3CZcg config= "<root> =DEBUG; unit=DEBUG" config= "<root> =DEBUG; unit=DEBUG" 20T14:08: 20Z" unsupported
Creating Juju controller "lxd" on lxd/localhost
Looking for packaged Juju agent version 2.3.5 for amd64
To configure your system to better support LXD containers, please see: https:/
Launching controller instance(s) on localhost/
- juju-00402b-0 (arch=amd64)
Installing Juju agent on bootstrap instance
Fetching Juju GUI 2.12.1
Waiting for address
Attempting to connect to 10.0.4.173:22
Connected to 10.0.4.173
Running machine configuration script...
Bootstrap agent now started
Contacting Juju controller at 10.0.4.173 to verify accessibility...
Bootstrap complete, "lxd" controller now available
Controller machines are in the "controller" model
Initial model "default" added
~ $ juju deploy cs:percona-cluster
Located charm "cs:percona-
Deploying charm "cs:percona-
~ $ juju run --unit percona-cluster/0 leader-get
leader-ip: 10.0.4.37
mysql.passwd: g6yHsw3fJysLKfw
root-password: g6yHsw3fJysLKfw
sst-password: JwMGKp7ysm9963x
~ $ juju model-config -m controller logging-
~ $ juju model-config logging-
~ $ juju upgrade-juju -m controller --agent-version 2.3.6
best version:
2.3.6
started upgrade to 2.3.6
~ $ juju upgrade-juju --agent-version 2.3.6
ERROR upgrade in progress (upgrade in progress)
~ $ juju status -m controller
Model Controller Cloud/Region Version Notes SLA
controller lxd localhost/localhost 2.3.6 upgrade in progress since "2018-04-
App Version Status Scale Charm Store Rev OS Notes
Unit Workload Agent Machine Public address Ports Message
Machine State DNS Inst id Series AZ Message
0 error 10.0.4.173 juju-00402b-0 xenial Running
Error in machine-0.log
2018-04-20 14:08:21 ERROR juju.upgrade upgrade.go:140 upgrade step "ensure container- image-stream config defaults to released" failed: The dotted field 'mysql.passwd' in 'settings. mysql.passwd' is not valid for storage. upgradesteps worker.go:379 upgrade from 2.3.5 to 2.3.6 for "machine-0" failed (will retry): ensure container- image-stream config defaults to released: The dotted field 'mysql.passwd' in 'settings. mysql.passwd' is not valid for storage.
2018-04-20 14:08:21 ERROR juju.worker.
Full machine-0.log -> http:// paste.ubuntu. com/p/GzGfyMtsv 6/
At the moment any juju controller that hosts a model with percona-cluster (the default for OpenStack installations) will get into this broken state when upgrading to 2.3.6