| 2023-10-18 13:56:20 |
Jeff Lane |
bug |
|
|
added bug |
| 2023-10-18 13:56:20 |
Jeff Lane |
attachment added |
|
regiond.log https://bugs.launchpad.net/bugs/2039687/+attachment/5710788/+files/regiond.log |
|
| 2023-10-18 14:04:50 |
Jack Lloyd-Walters |
maas: status |
New |
Triaged |
|
| 2023-10-18 14:17:20 |
Jeff Lane |
description |
Because of https://bugs.launchpad.net/maas/+bug/2039614, I tried reverting our MAAS snap from 3.4.0 to 3.3.4 using `snap revert maas` this morning hoping that would restore our MAAS environment to it's last working state.
Unfortunately, there appear to have been DB changes that make 3.3.4 incompatible with the DB structure in 3.4.0. This resulted in an unusable MAAS (I am unable to log in via web UI nor command line as the api server is dead).
So `snap revert` broke maas and as it isn't able to do backwards DB updates. I'm not sure the right way to address this, perhaps simply warn and not allow reverts of MAAS (and warn on updating that it isn't possible to revert)?
I've attached regiond showing the tracebacks from when MAAS tries to restart.
Bumping this back to 3.4.0 resolved the issue and I can get into MAAS both via web and CLI again. |
Because of https://bugs.launchpad.net/maas/+bug/2039614, I tried reverting our MAAS snap from 3.4.0 to 3.3.4 using `snap revert maas` this morning hoping that would restore our MAAS environment to it's last working state.
Unfortunately, there appear to have been DB changes that make 3.3.4 incompatible with the DB structure in 3.4.0. This resulted in an unusable MAAS (I am unable to log in via web UI nor command line as the api server is dead).
So `snap revert` broke maas as it isn't able to do backwards DB updates. I'm not sure the right way to address this, perhaps simply warn and not allow reverts of MAAS (and warn on updating that it isn't possible to revert)?
I've attached regiond log showing the tracebacks from when MAAS tries to restart.
Bumping this back to 3.4.0 resolved the issue and I can get into MAAS both via web and CLI again. |
|
| 2023-10-18 14:31:12 |
Jeff Lane |
description |
Because of https://bugs.launchpad.net/maas/+bug/2039614, I tried reverting our MAAS snap from 3.4.0 to 3.3.4 using `snap revert maas` this morning hoping that would restore our MAAS environment to it's last working state.
Unfortunately, there appear to have been DB changes that make 3.3.4 incompatible with the DB structure in 3.4.0. This resulted in an unusable MAAS (I am unable to log in via web UI nor command line as the api server is dead).
So `snap revert` broke maas as it isn't able to do backwards DB updates. I'm not sure the right way to address this, perhaps simply warn and not allow reverts of MAAS (and warn on updating that it isn't possible to revert)?
I've attached regiond log showing the tracebacks from when MAAS tries to restart.
Bumping this back to 3.4.0 resolved the issue and I can get into MAAS both via web and CLI again. |
Because of https://bugs.launchpad.net/maas/+bug/2039614, I tried reverting our MAAS snap from 3.4.0 to 3.3.4 using `snap revert maas` this morning hoping that would restore our MAAS environment to it's last working state.
Unfortunately, there appear to have been DB changes that make 3.3.4 incompatible with the DB structure in 3.4.0. This resulted in an unusable MAAS (I am unable to log in via web UI nor command line as the api server is dead).
So `snap revert` broke maas and as it isn't able to do backwards DB updates. I'm not sure the right way to address this, perhaps simply warn and not allow reverts of MAAS (and warn on updating that it isn't possible to revert)?
More properly, I had expected/hoped that updating the snap from 3.3.4 to 3.4.0 would create a backup of hte DB from 3.3.4 in case a revert was necessary, which hopefully the revert would then just reload the 3.3.4 version of the DB. Admittedly there's a potential for data loss there too if you've added machines or made changes post update, but the loss would be, IMO, far less than this case where it's simply impossible to roll back to a known working condition.
I've attached regiond showing the tracebacks from when MAAS tries to restart.
Bumping this back to 3.4.0 resolved the issue and I can get into MAAS both via web and CLI again. |
|
| 2023-10-18 15:35:03 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber Mauricio Faria de Oliveira |
