unknown object type "Charms"

[Curtis Hovey]

As seen in
    http://reports.vapour.ws/releases/2936/job/functional-candidate-client-1-22-server/attempt/8

Juju failed to deploy a charm because of: unknown object type "Charms" was first seen in using 1.25-alpha1 client created from master master talking to a 1.22.6 state-server. This might relate to fact that juju 1.24 uses the new charm store, and older Jujus use the old store, though the charm under test is a local dummy charm.

[Curtis Hovey (sinzui)]

The QA team will fix bug 1480299 to get the missing logs.

[Cheryl Jennings (cherylj)]

Was able to recreate. Can see this in the log:

machine-0: 2015-07-31 15:37:22 DEBUG juju.apiserver apiserver.go:265 <- [6] user-admin@local {"RequestId":4,"Type":"Charms","Request":"IsMetered"}
machine-0: 2015-07-31 15:37:22 DEBUG juju.apiserver apiserver.go:272 -> [6] user-admin@local 213.938us {"RequestId":4,"Error":"unknown object type \"Charms\"","ErrorCode":"not implemented","Response":{}} Charms[""].IsMetered

The charm deployment did continue and complete successfully. Looking more at the metering code...

[Cheryl Jennings (cherylj)]

When deploying a charm, it calls registerMeteredCharm after calling the API to do the deploy and returns an error for the whole deployment if it is unable to register the charm for metering.

It probably should print out a warning that the juju version doesn't support metering, rather than returning an error.

Given that the deploy actually goes through, the severity of this bug could be reduced while I work on the fix.

[Cheryl Jennings (cherylj)]

Review request: http://reviews.vapour.ws/r/2287/

[Canonical Juju QA Bot (juju-qa-bot)]

Juju-CI verified that this issue is Fix Released in juju-core master:
    http://reports.vapour.ws/releases/2946