all agents except machine agent logging "INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3" every 15 minutes following "juju upgrade-juju"

[Paul Collins]

I noticed that all juju agents, except the machine agents, on every unit in an environment recently "juju upgrade-juju"'d to 1.18.4 are logging "INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3" every 15 minutes, i.e.:

ubuntu@juju-prod-ue-et-machine-20:~$ tail -n3 /var/log/juju/*.log
==> /var/log/juju/machine-20.log <==
2014-12-08 22:15:16 INFO juju.worker.deployer deployer.go:102 checking unit "e-t-nrpe-errors-postgresql/1"
2014-12-08 22:15:16 INFO juju.worker.deployer deployer.go:102 checking unit "e-t-landscape/17"
2014-12-08 22:15:20 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3

==> /var/log/juju/unit-e-t-ksplice-17.log <==
2014-12-10 02:02:24 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3
2014-12-10 02:17:21 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3
2014-12-10 02:32:23 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3

==> /var/log/juju/unit-e-t-landscape-17.log <==
2014-12-10 02:02:24 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3
2014-12-10 02:17:21 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3
2014-12-10 02:32:23 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3

==> /var/log/juju/unit-e-t-nrpe-errors-postgresql-1.log <==
2014-12-10 02:02:24 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3
2014-12-10 02:17:21 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3
2014-12-10 02:32:23 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3

==> /var/log/juju/unit-e-t-postgresql-0.log <==
2014-12-10 02:02:24 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3
2014-12-10 02:17:21 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3
2014-12-10 02:32:23 INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3
ubuntu@juju-prod-ue-et-machine-20:~$ _

2014-12-08 22:15:20 per the machine agent's log is when the "juju upgrade-juju" was originally performed, which seems to have completed:

$ juju status | awk '/agent-version: / { print $2 }' | sort -u
1.18.4.3
$ _

[Curtis Hovey (sinzui)]

1.18.4.3 is sort if impossible for an env using streams. It it can happen when upgrade-juju is called from a machine with a juju development env where a .1, .2, .3 can be built and uploaded (using --upload-tools).

IS the env using --upload-tools, does the host that ran upgrade-juju have the juju tree and golang installed?

[Paul Collins (pjdc)]

The environment is not using streams for tools. We do not have a juju tree or Go development environment installed. The upgrade was done with --upload-tools, and apparently required multiple attempts. (I will obtain more information on this.)

[Curtis Hovey (sinzui)]

This bug is likely caused by upload-tools which circumvents official streams by creating unique agents and publishing them to a local container.. The issue might not even be in juju 1.22 because agents are stored on and retrieved from the state-server.

[Anastasia (anastasia-macmood)]

Marking as invalid since the area has been substantially changed in currently supported Juju versions - 1.25 and 2.0.