annotations and charms not working apiserver

Bug #1414086 reported by Kapil Thangavelu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Invalid
Undecided
Unassigned

Bug Description

applies to charms and annotations facades

        return self.rpc._rpc({
            "Type": "Charms",
            "Request": "List",
            "Params": {"Names": names}})

gets

jujuclient.EnvError: <Env Error - Details:
 { u'Error': u'unknown object type "Charms"',
    u'ErrorCode': u'not implemented',
    u'RequestId': 1,
    u'Response': { }}

same code works for every other facade, using a trunk checkout. I do see the Charms facade in the login data, ie.

{u'EnvironTag': u'environment-fb933e3d-5293-486a-8ff9-7ac565271c35',
 u'Facades': [{u'Name': u'Action', u'Versions': [0]},
              {u'Name': u'Agent', u'Versions': [0, 1]},
              {u'Name': u'AllWatcher', u'Versions': [0]},
              {u'Name': u'Annotations', u'Versions': [1]},
              {u'Name': u'Backups', u'Versions': [0]},
              {u'Name': u'CharmRevisionUpdater', u'Versions': [0]},
              {u'Name': u'Charms', u'Versions': [1]},

Revision history for this message
Kapil Thangavelu (hazmat) wrote :

also to note the unit tests for the client never use anything but mocks, and the cli doesn't use either of these apis facades.

Revision history for this message
Kapil Thangavelu (hazmat) wrote :

root issue ended up being a little different. my client wasn't explicitly passing api facade versions, which meant i was getting version 0 of the facade, per go default int value. all of which worked fine except when the facade didn't have a version 0 as is the case for the Annotations, Charms, HA on trunk.

marking as invalid

Changed in juju-core:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.