On Tue, Apr 8, 2014 at 6:58 PM, Ian Booth <email address hidden> wrote:
> I've found the cause for one of the errors shown in the logs:
>
> 2014-04-04 16:31:59 ERROR juju.worker environ.go:56 loaded invalid
> environment configuration: storage-port: expected int, got float64(8040)
>
> There's a configuration issue that needs to be fixed for manual provider.
> I'm not yet certain if this error prevents the various moving parts from initialising correctly in order to cause the observed symptoms, but the error needs to be fixed nonetheless.
Thanks Ian.
If direct access to the systems in question would help, grab me on IRC
(dannf). We've got an openstack setup where its relatively easy/quick to launch
new instances.
On Tue, Apr 8, 2014 at 6:58 PM, Ian Booth <email address hidden> wrote:
> I've found the cause for one of the errors shown in the logs:
>
> 2014-04-04 16:31:59 ERROR juju.worker environ.go:56 loaded invalid
> environment configuration: storage-port: expected int, got float64(8040)
>
> There's a configuration issue that needs to be fixed for manual provider.
> I'm not yet certain if this error prevents the various moving parts from initialising correctly in order to cause the observed symptoms, but the error needs to be fixed nonetheless.
Thanks Ian.
If direct access to the systems in question would help, grab me on IRC
(dannf). We've got an openstack setup where its relatively easy/quick to launch
new instances.