Migrations are tested in sequence, and skipping several generations of
MAAS releases may not work, even though we take steps to make sure that
the migration process is smooth and painless. The original issue relates
to a problem in the migration scripts that used the logic in MAAS itself
to perform
** Changed in: maas
Milestone: 3.5.x => 3.6.x
** Also affects: maas/3.5
Importance: Undecided
Status: New
** Changed in: maas/3.5
Status: New => Won't Fix
** Changed in: maas/3.5
Importance: Undecided => Medium
--
You received this bug notification because you are a mem
** Tags added: bug-council
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880495
Title:
Upgrade from 1.95 to 2.35 failure because column maasserver_domain.ttl
does not exist
To manage notificatio
** Also affects: maas/3.3
Importance: Undecided
Status: New
** Also affects: maas/3.4
Importance: Undecided
Status: New
** Changed in: maas/3.3
Status: New => Won't Fix
** Changed in: maas/3.4
Status: New => Won't Fix
** Changed in: maas/3.3
Importance: Unde
** Changed in: maas
Milestone: 3.4.x => 3.5.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880495
Title:
Upgrade from 1.95 to 2.35 failure because column maasserver_domain.ttl
does not exist
** Changed in: maas
Assignee: Felipe Reyes (freyes) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880495
Title:
Upgrade from 1.95 to 2.35 failure because column maasserver_doma
** Changed in: maas
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880495
Title:
Upgrade from 1.95 to 2.35 failure because column maasserver_domain.ttl
does not
** Merge proposal linked:
https://code.launchpad.net/~freyes/maas/+git/maas/+merge/384587
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880495
Title:
Upgrade from 1.95 to 2.35 failure because co
** Changed in: maas
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880495
Title:
Upgrade from 1.95 to 2.35 failure because column maasserver_doma
Yup, as Felipe links I think the problem here is that we are using the
models within the database migration. However, the models assume all
migrations have been applied. The call to
`maasserver.models.dnsresource.get_default_domain()` should be replaced
with something that doesn't use the models.
I could reproduce this issue locally, and this is what I believe is
happening with this environment (and not for other upgrades) is that the
database has no domains defined for the interfaces related, so this
piece of code [0] is falling into the "else" section which calls
get_default_domain() meth
11 matches
Mail list logo
