Incompatible cookie format change

Bug #1511717 reported by Aaron Bentley
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Casey Marshall
juju-core
Fix Released
High
Casey Marshall
1.25
Fix Released
High
Casey Marshall
1.26
Fix Released
Critical
Casey Marshall

Bug Description

As ~jog writes:
  Starting with revision build 3243 (http://reports.vapour.ws/releases/3243) tests are failing due to a change in cookie format. There
  is a per user cookie file ($HOME/.go-cookies), which means Juju clients of different versions will collide.

Issue
http://reports.vapour.ws/releases/issue/56329c09749a5627f93a5302

Aaron Bentley (abentley)
tags: added: compatibility
Revision history for this message
James Tunnicliffe (dooferlad) wrote :

Deleting the cookie file (which was empty for me) worked around the problem.

Revision history for this message
Aaron Bentley (abentley) wrote :

@dooferlad, it's good to note workarounds, but we need this bug to be fixed. It's breaking testing, it will break users, and the workaround we tried also breaks testing.

tags: added: blocker ci
Revision history for this message
Casey Marshall (cmars) wrote :

I think we should delete the cookies out of the CI workspace and close this bug. There is no guarantee of compatibility until we cut a release. There is no compatibility issue with prior releases of Juju (< 1.26), because this is a new feature.

We should add a CI test for cookie compatibility once 1.26 branches, but that is a separate concern to this specific bug I think.

Changed in juju-core:
status: Triaged → Invalid
Revision history for this message
Aaron Bentley (abentley) wrote :

Trunk should always be releaseable. Trunk should not break CI. Valid bug.

Changed in juju-core:
status: Invalid → Triaged
Revision history for this message
Casey Marshall (cmars) wrote :

Re-opening until I can confirm this wouldn't be a problem for 1.25.0 -> 1.26.x, just realized that went out.

Revision history for this message
Casey Marshall (cmars) wrote :

Releaseable yes. Fully compatible across each commit to master, no. We make changes to API, state models, all kind of things in master until we branch for a release.

We do need to ensure compatibility across releases.

Revision history for this message
Aaron Bentley (abentley) wrote :

BTW, John George did try to work around it, but those workarounds themselves broke CI.

Revision history for this message
Aaron Bentley (abentley) wrote :

Please keep it open until you convince QA that it is not a critical regression and until it does not break CI.

Revision history for this message
Casey Marshall (cmars) wrote :

Ah, this will indeed be an issue for 1.25 -> 1.26. We'll need to add support for migrating the cookie jar. Thanks.

Revision history for this message
Casey Marshall (cmars) wrote :
Revision history for this message
Casey Marshall (cmars) wrote :

Per discussion with mgz, I'm going to follow this up with an update targeting 1.25.1, that will address 1.26 -> 1.25 compatibility.

Changed in juju-core:
status: Triaged → Fix Committed
assignee: nobody → Casey Marshall (cmars)
Revision history for this message
Casey Marshall (cmars) wrote :
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote : Fix Released in juju-core master

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

Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju-core:
assignee: nobody → Casey Marshall (cmars)
importance: Undecided → High
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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