| 2017-11-17 20:04:54 |
Mike Pontillo |
description |
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".
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. |
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. |
|
