Spurious "juju run after upgrade succeeded" when deploy_job is run without --upgrade

Bug #1450585 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-ci-tools
Fix Released
Low
Martin Packman

Bug Description

$ ./deploy_job.py charm-testing-joyent ~/sandbox/logs test-job --new-juju-bin /usr/bin
juju --show-log bootstrap -e test-job --constraints mem=2G
2015-04-30 17:08:05 INFO juju.cmd supercommand.go:37 running juju [1.22.1-vivid-amd64 gc]
2015-04-30 17:08:05 WARNING juju.environs config.go:127 Config attribute "tools-metadata-url" (https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e3464589dc1145dfeaac60/juju-dist/tools) is deprecated.
It is replaced by "agent-metadata-url" attribute.
Your configuration should be updated to set "agent-metadata-url" as follows
agent-metadata-url: https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e3464589dc1145dfeaac60/juju-dist/tools.

...

2015-04-30 13:13:10 INFO juju run after upgrade succeeded: [{u'MachineId': u'1', u'Stderr': u"Warning: Permanently added '10.112.5.15' (ECDSA) to the list of known hosts.\r\n", u'Stdout': u'Linux\n'}, {u'MachineId': u'2', u'Stderr': u"Warning: Permanently added '10.112.4.236' (ECDSA) to the list of known hosts.\r\n", u'Stdout': u'Linux\n'}]

Related branches

Aaron Bentley (abentley)
Changed in juju-ci-tools:
assignee: nobody → Martin Packman (gz)
Martin Packman (gz)
Changed in juju-ci-tools:
status: Triaged → In Progress
Martin Packman (gz)
Changed in juju-ci-tools:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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