Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Amulet skips local charms when uncommitted bzr changes are present #55
Comments
marcoceppi
added this to the 1.19.1 milestone
Dec 8, 2014
marcoceppi
added
the
bug
label
Dec 8, 2014
This was referenced Dec 11, 2014
|
Fixed by juju-deployer 0.5.1 and amulet 6a15ee1 |
tvansteenburgh
closed this
Aug 18, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
chuckbutler commentedDec 8, 2014
When deploying a charm in bundle format from a dirty directory - it skips loading the local charm and instead resorts to using the store charm. A known work-around is to commit the changes pre-emptively before executing the test.
Conditions that exhibited the behavior:
The following bundle yaml was loaded in an amulet test for hdp-hive
Bundletester was executed from the charm directory:
$ bundletester -F -l DEBUG -v -e hpcloudOutput snippet from juju status:
current bzr status in directory: