[1.9.0] Document need to recommission nodes that were deployed when upgrading from 1.8.3

[Adam Collard]

The release notes stated that "If upgrading from MAAS 1.8, only VM nodes with VirtIO storage devices need to be re-commissioned." - however even with real physical hardware, one still needs to recommission to avoid MAAS UI complaining about missing networks, missing disks and preventing deployment.

Re-commissioning a node remedied these complaints.

[Andres Rodriguez (andreserl)]

Hi Adam,

Do you have any logs or screenshots displaying such behavior. Can you provide information about the hardware which you saw this issue with? Was the hardware deployed at upgrade time?

Thanks.

[Chris Glass (tribaal)]

When deploying an "ubuntu" charm to a migrated (but not re-provisionned) node I get the following in juju debug-log:

http://pastebin.ubuntu.com/14574935/

The maas logs (/var/log/maas.log) do not show any errors:

http://pastebin.ubuntu.com/14574946/

Re-commissioning the node(s) fixes the issue.

[Chris Glass (tribaal)]

The hardware was not deployed at upgrade time - it was preexisting and used on 1.8.

[Adam Collard (adam-collard)]

Hi Andres,

Yes at the time of upgrade the node which later had no storage nor network was Deployed. I released it post upgrade. The node in the screenshot was Ready at upgrade time, and /has/ storage, but no network.

Adam

[Chris Glass (tribaal)]

As for the hardware question, here is the output of "maas <server> nodes list":

https://paste.ubuntu.com/14575408/

[Andres Rodriguez (andreserl)]

Ok, so I think I know what's going on here.

Provided the hardware was deployed at the time of upgrade, MAAS cannot really update the storage/network model of a deployed node because it won't really reflect reality.

When the hardware is released, we can't really determine this node was deployed when the upgrade happen, and that its model needs to be udpated. I thought I had documented this, however, if not, I'll proceed to document this; but will also check with Blake/Mike.

[Andres Rodriguez (andreserl)]

We believe that this is not longer an issue in the latest releases of MAAS. If you believe this is still an issue, please re-open this bug report and target it accordingly.