remove-application has unexpected output

[Charles Butler]

Juju Version:
Juju 2.0-beta11

What I did:

juju deploy cs:~containers/bundle/beats-core
juju remove-application filebeat
juju remove-application topbeat

What I expected to happen:

Juju to remove the applications: subordinate charms which have not been related to any principal services yet. (read: un-deployed, only allocated in the model)

What happened:

ERROR application "topbeat" not found (not found)
ERROR application "filebeat" not found (not found)

The removal did work, however I received error output which lead me to believe there was a problem removing the charm.

[Anastasia (anastasia-macmood)]

I have done further investigation with Juju 2.1.0.

If I call remove-application when application is shown as "active", I do not get the error described above.

If I call remove-application when application is shown as "waiting", I get the error.

I believe that this is coming from the logic that retrieves application details: Juju must be filtering based on application status of 'Active'.

The application will get removed in both situations. However, I agree that the error is misleading.

[Anastasia (anastasia-macmood)]

This behavior is observed on any application irrespective of relation: subordinate or not, does not matter. I've renamed the bug.

[Anastasia (anastasia-macmood)]

I have not seen this error with 2.2.0. I suspect that the behavior was fixed as part of another bug fix.