Could someone double check this please

[Jesse Meek]

After upgrading from 1.20.12-trusty-amd64 to master (commit 
2807fed7fad5619079c98ea105674d8a724d2e66), all unit logs continually 
spew errors similar to the following:

// ~/.juju/local/log/unit-mysql-0.log
2014-11-26 09:09:07 ERROR juju.worker runner.go:219 exited "uniter": 
failed to initialize uniter for "unit-mysql-0": cannot initialize hook 
commands in "1.22-alpha1.1-trusty-amd64": symlink 
1.22-alpha1.1-trusty-amd64/jujud 1.22-alpha1.1-trusty-amd64/action-fail: 
no such file or directory

After upgrade, I am unable to destroy a service. Would someone be able 
to try the following on their box to confirm that I don't have something 
screwy on mine:

# with old juju i.e. /usr/bin/juju
juju switch local
juju destroy-environment --force --yes local

juju bootstrap

juju deploy mysql
juju deploy mediawiki
juju add-relation mysql:db mediawiki:db

# wait for env to be ready. Then with juju built from trunk:

juju upgrade-juju --upload-tools
juju destroy-service mediawiki


If I run the upgrade again after I've issued the destroy-service 
command, the service then gets removed. I imagine the dying service is 
caught as the watcher has to reassess entities and states when it starts 
up after the upgrade. It's EOD here, I'll pick up on this in the 
morning. Thank you in advance.

Jess