Re: Amulet doesn't find deployed units

The amulet Talisman code only creates sentries for services (applications) that are in the deployment schema. The Kubernetes Core bundle tests just don't work. I looked at the Canonical Kubernetes

Re: Amulet doesn't find deployed units

I'm sure the bundle is being deployed, I checked with `juju status`. When that error message happens, both limeds and docker are already deployed, even though the error happens at the first "add" line. I'll post the debug output tomorrow. Op maandag 16 januari 2017 heeft Tim Van Steenburgh < tim.

Re: Amulet doesn't find deployed units

You're right, deployment.add() isn't needed - the sentries get parsed out of the real-time Juju status. Are you sure the bundle is actually being deployed before your test is run? You can pass -vl DEBUG for more verbose output. I wonder if you need to set "bundle_deploy: true" instead of "bundle_

Re: Amulet doesn't find deployed units

Hi Tim The tests for the kubernetes-core bundle don't do `deployment.add..`. I thought that bundle was a good start for my tests since the bundle is promulgated.. Does this mean that the tests for

Re: Amulet doesn't find deployed units

You need to define the services in the deployment, even if they are already deployed by bundletester. So for example: cls.deployment.add('docker') cls.deployment.add('limeds') On Mon, Jan 16, 2017 at 10:15 AM, Merlijn Sebrechts < merlijn.sebrec...@gmail.com> wrote: > Hi all > > > Code: https://g