lp:~ack/landscape-client/clear-hash-ids-on-resync

Branch merges

Propose for merging

No branches dependent on this one.

Rejected for merging into lp:~landscape/landscape-client/trunk

Landscape: Pending requested 2014-10-01

Landscape: Pending requested 2014-10-01

Diff: 63 lines (+14/-19)

2 files modified

landscape/package/reporter.py (+1/-1)
landscape/package/tests/test_reporter.py (+13/-18)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

789. By Alberto Donato on 2014-09-30

Clean hash-ids on resync.

788. By Andreas Hasenack on 2014-09-29

Version bump

787. By Free Ekanayaka on 2014-09-29

Merge fix-apt-preferences-hides-upgrades [f=1374338] [r=tealeg,ack] [a=Free Ekanayaka]
This branch:

- makes the client clear the hash->id requests table when resynchronizing,
  which was not done before because of possible pending messages delivering
  that request to a different server. Now that we have session IDs those
  outgoing messages will be discarded, so there's no need for the trick.

- adds a missing test that fails if one removes the "not version.package.is_upgradable"
  clause of the if statement in facade.py line line 422.

786. By Free Ekanayaka on 2014-09-26

Merge drop-old-juju-info-data [f=1373284] [r=bjornt,ack] [a=Free Ekanayaka]
Stop parsing the .json files in the juju directory and just parse
the single file that the charm now generates.

785. By Free Ekanayaka on 2014-09-18

Merge drop-juju-info-list [f=1369635] [r=ack,tealeg] [a=Free Ekanayaka]
Drop the code that sends the legacy juju-info-list message/field,
which we don't use anymore in the server.

784. By Free Ekanayaka on 2014-09-02

Merge juju-machine-registration [f=1362506] [r=adam-collard,ack] [a=Free Ekanayaka]
This branch:

- Bumps the server API to 3.3: this will let us introduce a new schema
  for the juju-info registration field, since we have released clients
  out there that could potentially send the old juju-info schema (although
  they'd need to be deployed with an older version of the client charm,
  so it's more a theoretical situation than one that can happen in practice).
  A server branch has been pushed to bump the server to API 3.3. as well.

- Include the machine ID information in the registration message if the server
  is capable of handling it.

783. By Free Ekanayaka on 2014-08-28

Merge juju-machine-info [f=1360282] [r=adam-collard,ack] [a=Free Ekanayaka]
This branch changes the get_juju_info utility to return information
about the Juju machine ID the client runs in. Since we're in the
middle of the transition, both the old info with unit names and the
new info with the machine ID are returned. When the transition completes
in the server too the old info can be dropped.

782. By Free Ekanayaka on 2014-08-22

Merge handle-server-api [f=1342649] [r=ack,adam-collard] [a=Free Ekanayaka]
This branch modifies the broker's MessageExchange and MessageStore
to handle a new 'server-api' field which is going to be included
in every payload the server sends to the client. This new field
will inform the client about which message API the server is
capable of handling, so we can finally properly support newer
clients talking to older server even in cases where there are
message schemas changes.

781. By Free Ekanayaka on 2014-07-21

Merge drop-provisioning-registration-2 [f=1344054] [r=tribaal,ack] [a=Free Ekanayaka]
Drop unused provisioning registration code.

780. By Free Ekanayaka on 2014-07-18

Merge drop-provisioning-registration [f=1343147] [r=tribaal,tealeg] [a=Free Ekanayaka]
This is the first of two branches that drop all provisioning-related
code left in the client.