After running juju in production for 6 months an issue with the available disk space has cropped up out of the blue. With a lack of directly specified basic system requirements for juju cloud controllers the root drive (8GB) is now filled to 95%.

Whilst exploring options to upgrade disk space it came to my attention that the backup restore process is broken!!

I am currently running juju controllers on version 2.3.5 (a version this bug should be cleared up for: https://bugs.launchpad.net/juju/+bug/1616704) however whenever i run the following command: juju restore-backup --constraints tags="tag" --file "juju-maas-backup.tgz" -m controller --debug

I receive this output:

09:53:04 INFO juju.cmd supercommand.go:56 running juju [2.3.5 gc go1.10] 09:53:04 DEBUG juju.cmd supercommand.go:57 args: []string{"juju", "restore-backup", "--constraints", "tags=tag", "--file", "juju-maas-backup.tgz", "-m", "controller", "--debug"} 09:53:05 INFO juju.juju api.go:67 connecting to API addresses: [***.***.***.***:17070 [2a01:6200:0:1004:5054:ff:fee1:c097]:17070] 09:53:05 DEBUG juju.api apiclient.go:843 successfully dialed "wss://***.***.***.***:17070/model/30eacda9-25d0-48d1-81b3-e300e03c16dc/api" 09:53:05 INFO juju.api apiclient.go:597 connection established to "wss://***.***.***.***:17070/model/30eacda9-25d0-48d1-81b3-e300e03c16dc/api" 09:53:05 DEBUG juju.api.backups restore.go:54 Will attempt to call 'PrepareRestore' 09:53:05 INFO juju.juju api.go:67 connecting to API addresses: [***.***.***.***:17070 [2a01:6200:0:1004:5054:ff:fee1:c097]:17070] 09:53:05 DEBUG juju.api apiclient.go:843 successfully dialed "wss://***.***.***.***:17070/model/30eacda9-25d0-48d1-81b3-e300e03c16dc/api" 09:53:05 INFO juju.api apiclient.go:597 connection established to "wss://***.***.***.***:17070/model/30eacda9-25d0-48d1-81b3-e300e03c16dc/api" 09:53:06 DEBUG juju.api monitor.go:35 RPC connection died 09:53:06 DEBUG juju.api.backups restore.go:75 Server is now in 'about to restore' mode, proceeding to upload the backup file 09:53:06 DEBUG httpbakery client.go:244 client do PUT https://***.***.***.***:17070/model/30eacda9-25d0-48d1-81b3-e300e03c16dc/backups { 09:53:31 DEBUG httpbakery client.go:246 } -> error <nil> 09:53:31 DEBUG juju.api.backups restore.go:119 Attempting Restore of "20181009-170043.d22311e8-284f-433a-80be-6829a3fa867f" 09:53:31 INFO juju.juju api.go:67 connecting to API addresses: [***.***.***.***:17070 [2a01:6200:0:1004:5054:ff:fee1:c097]:17070] 09:53:31 DEBUG juju.api apiclient.go:843 successfully dialed "wss://***.***.***.***:17070/model/30eacda9-25d0-48d1-81b3-e300e03c16dc/api" 09:53:31 INFO juju.api apiclient.go:597 connection established to "wss://***.***.***.***:17070/model/30eacda9-25d0-48d1-81b3-e300e03c16dc/api" 09:53:43 DEBUG juju.api monitor.go:35 RPC connection died 09:54:31 DEBUG juju.api monitor.go:55 health ping failed: connection is shut down

It would appear to me that there is some bug present in version 2.3.5 causing back restores to fail.

Can anyone offer advice for this please?

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.