Juju Charms Collection
landscape-client package

Setting origin to PPA post-install does not update APT sources or landscape-client

Bug #1668166 reported by James Hebden
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
landscape-client-charm
Fix Committed
Medium
Björn Tillenius
landscape-client (Juju Charms Collection)
Fix Committed
Medium
Björn Tillenius

Bug Description

Current trunk (rev 55 lp:charms/trusty/landscape-client)
Ubuntu Xenial 16.04

Changing the origin setting does nothing post-install, as the origin config entry is only used when running the install hook. This makes setting the origin post-install do nothing, and means upgrades to Landscape client can not be performed unless the upstream package is upgraded. Switching to a package contained in a newer PPA is not possible.

Related branches

lp://staging/~bjornt/landscape-client-charm/update-source
🤖 Landscape Builder: Approve (test results)
Free Ekanayaka (community): Approve
Alberto Donato: Approve
Diff: 426 lines (+209/-37)
4 files modified
hooks/hooks.py (+13/-6)
hooks/install.py (+18/-19)
hooks/stubs.py (+81/-0)
hooks/test_hooks.py (+97/-12)
James Hebden (ec0)
tags: added: canonical-bootstack
removed: bootstack-is
David Britton (dpb)
Changed in landscape-client-charm:
status: New → Triaged
importance: Undecided → Medium
Changed in landscape-client (Juju Charms Collection):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
David Britton (dpb) wrote :

Hi James -- Is changing the PPA post deploy a regular part of the bootstack process, or something that you noticed as a one-off?

Revision history for this message
James Hebden (ec0) wrote :

Hi David,

Given we primarily work with LTS releases of Ubuntu in customer clouds, it's common for us to use the stable PPAs for various Canonical infrastructure tools to get newer tooling on existing clouds.

Often this approach is used on even the current LTS, given the specific major versions of specific packages will often be locked in at launch.

Landscape has been tricky in the past for us to upgrade in this fashion, as the charm does not respond to changes of origin. If we could get this addressed it would be a huge help when maintaining bootstack clouds ongoing. The current process would be to manually SSH to each unit and add the PPA, and upgrade the client software - Which isn't very jujuy.

Short answer would be that we need this ongoing, it's not a one-off.

- James

Björn Tillenius (bjornt)
Changed in landscape-client-charm:
status: Triaged → In Progress
assignee: nobody → Björn Tillenius (bjornt)
Revision history for this message
Björn Tillenius (bjornt) wrote :

Is it enough if we handle upgrades only? Adding new PPAs and upgrading landscape-client we can do reasonably easily. But downgrading to a lower version is a bit tricky, so I'd like to not care about downgrading for now.

🤖 Landscape Builder (landscape-builder)
Changed in landscape-client-charm:
status: In Progress → Fix Committed
Revision history for this message
Björn Tillenius (bjornt) wrote :

The fix is now available in the edge channel as cs:landscape-client-29.

Pending QA to be released into the stable channel.

Changed in landscape-client (Juju Charms Collection):
status: Triaged → Fix Committed
assignee: nobody → Björn Tillenius (bjornt)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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