ubuntu-repository-cache: hard-coded cron path to juju-run is wrong for juju v1.24

Bug #1455649 reported by Robert C Jennings on 2015-05-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-repository-cache (Juju Charms Collection)
Critical
Dan Watkins

Bug Description

Seen on juju-1.24-beta1.2, juju-run has moved from /usr/local/bin to /usr/bin.

The charm is using an absolute path to juju-run when creating the cronjob on the leader which will be incorrect for juju 1.24.

The current contents of /etc/cron.d/ubuntu-repository-cache-sync would look like:

/usr/local/bin/juju-run ubuntu-repository-cache/0 /var/lib/juju/agents/unit-ubuntu-repository-cache-0/charm/hooks/ubuntu-repository-cache-sync

Need to change this to call juju-run without the path and just depend on $PATH.

Related branches

Robert C Jennings (rcj) on 2015-05-15
Changed in ubuntu-repository-cache (Juju Charms Collection):
assignee: nobody → Robert C Jennings (rcj)
status: New → In Progress
Robert C Jennings (rcj) on 2015-05-29
Changed in ubuntu-repository-cache (Juju Charms Collection):
importance: Undecided → Critical
Marco Ceppi (marcoceppi) wrote :

In generaly you should never hard code paths for juju tools as they will (and have in the past and now) change. Best to setup proper path envs in cron instead

Changed in ubuntu-repository-cache (Juju Charms Collection):
assignee: Robert C Jennings (rcj) → Dan Watkins (daniel-thewatkins)
Robert C Jennings (rcj) wrote :

Thanks Marco, that's the plan to remove the hard-coded path in the cron template.

José Antonio Rey (jose) on 2015-06-04
Changed in ubuntu-repository-cache (Juju Charms Collection):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers