[2.3] Strange behavior when removing a secondary controller

[Mike Pontillo]

I deployed a machine in MAAS, then ran "snap install maas" and configured it as a secondary controller.

After upgrading my primary MAAS, a notification appeared: "Controller secondary is running an older version of MAAS." Fine; I decided I no longer wanted to use it. So I ran "snap remove maas" on the secondary controller.

A few issues resulted:

(1) The controller was shown as "no longer connected" and I had to delete it manually. It might be nice if, when uninstalling the snap, the controller is automatically unregistered.

(2) The aforementioned notification remains until I dismiss it, even though the controller no longer exists.

(3) The "Status" field is set to "ubuntu-core/16", even though I initially deployed Ubuntu Classic to the machine the controller was running on.

[Mike Pontillo (mpontillo)]

Even if (1) and (3) could be considered Invalid, (2) is still a real bug.

[Andres Rodriguez (andreserl)]

1. To my knowledge there's no way we can notify to the running software on the snap, that we were removing ourselves, which would prevent that from happening. So we always need to manually delete it.

2. IIRC, these notifications don't auto-dismiss, and I dont think we hvae a mecahanism for that.

3. Already a bug filed for that. The snap running on ubuntu classic reports its running ubuntu core. :/

[Mike Pontillo (mpontillo)]

Yeah, we'd have to write some post-delete logic to remove the notifications. Notifications are modeled in a pretty generic way, so I don't think an automatic cascade delete would work.

But it's a minor issue, and easily dismissed.