The new images for focal, jammy and noble are out. This issue is
resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106671
Title:
Deployments using a bonded interface on the "MAAS" management
** Changed in: maas
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106671
Title:
Deployments using a bonded interface on the "MAAS" management network
are br
@Qwaszx the situation at the moment is the following:
- focal: both candidate and stable streams are broken
- jammy: both candidate and stable streams contain the fix
- noble: only candidate stream has the fix. Stable is still affected
(stable is https://images.maas.io/ephemeral-v3/stable/)
(cand
I rebuilt the latest cloud-image adding the new cloud-init package and I
deployed it 5 times: it always worked. So from our side it's looking
good.
** Tags added: verification-done-focal
** Tags removed: verification-needed-focal
--
You received this bug notification because you are a member of
We'll take care of testing the new package in the following way:
1) we use the internal tools to pick the latest image from
http://cloud-images.ubuntu.com/daily/ and convert it to the MAAS format
2) we try to deploy it and we'll ensure that we can reproduce the issue
then
1) we rebuild the imag
@Andreas deploying machines with bonded interfaces is broken since 2
months and many community members and customers are waiting for the fix.
This fix was supposed to work and the candidate image for jammy was
recently built but it's still broken for other cloud-init issues - this
is why multiple p
> a) who builds the maas images on images.maas.io, assuming that's where
maas fetches them by default from?
CPC
> b) Do you have the serial/hash/id of a focal image that works?
Unfortunately https://images.maas.io/ephemeral-v3/stable/focal/amd64/
has only the latest 4, and all of them are not wo
Landing the new cloud-init to the archive is not enough if we don't
rebuild the images. So I believe we should revert the focal image to a
version that is fully working on images.maas.io, unless we have a strong
reason not to do it.
--
You received this bug notification because you are a member o
** 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/2106671
Title:
Deployments using a bonded interface on the "MAAS" management network
are broken
To manage notifications ab
I confirm both focal and jammy work fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this bug go to:
https:
I'm on it for the testing part
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this bug go to:
https://bugs.lau
You can either create a simplestream mirror and remove the problematic
image or add `/var/snap/maas/current/preseeds/curtin_userdata`
```
#cloud-config
debconf_selections:
maas: |
{{for line in str(curtin_preseed).splitlines()}}
{{line}}
{{endfor}}
late_commands:
maas: [wget, '--no-proxy'
I confirm the version in ppa:cloud-init-dev/daily works fine (I tested
jammy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106671
Title:
Deployments using a bonded interface on the "MAAS" manageme
I just checked both stable and candidate images and they are working
fine on my end.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since Feb 4 update
To ma
** Changed in: maas
Assignee: (unassigned) => Jacopo Rota (r00ta)
** Changed in: maas
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092232
Title:
Be aware that if you are using OVS you are probably hitting
https://bugs.launchpad.net/maas/+bug/2103903
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since
@patricia that one should be fixed by
https://bugs.launchpad.net/maas/+bug/2104530 . The hotfix will be rolled
out to TOR3 tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092232
Title:
unab
output of dmesg after I executed `sudo lsblk`
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/maas/+bug/2092232/+attachment/5868933/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Changed in: maas
Status: In Progress => Invalid
** Changed in: maas
Assignee: Jacopo Rota (r00ta) => (unassigned)
** Changed in: maas
Milestone: 3.6.x => None
** Changed in: maas
Importance: High => Undecided
--
You received this bug notification because you
Output of `strace lsblk`
** Attachment added: "strace_lsblk.txt"
https://bugs.launchpad.net/maas/+bug/2092232/+attachment/5868758/+files/strace_lsblk.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I believe curtin is failing to install because `lsblk` is returning
empty output.
I installed Plucky on a P9 VM and indeed I get no output when I execute
`lsblk` (see screenshot)
** Attachment added: "Screenshot from 2025-04-01 22-39-54.png"
https://bugs.launchpad.net/maas/+bug/2092232/+attac
** Merge proposal linked:
https://code.launchpad.net/~r00ta/maas/+git/maas/+merge/479064
** Changed in: maas/3.4
Assignee: (unassigned) => Jacopo Rota (r00ta)
** Changed in: maas/3.4
Status: Triaged => Fix Committed
--
You received this bug notification because you are a
** Changed in: maas/3.5
Milestone: 3.4.x => 3.5.x
** Changed in: maas/3.4
Milestone: 3.5.x => 3.4.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089185
Title:
Releasing fails with latest
** Tags removed: 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/2089185
Title:
Releasing fails with latest cloud-init on image 20241113
To manage notifications about this bug go to:
http
** Merge proposal linked:
https://code.launchpad.net/~r00ta/maas/+git/maas/+merge/478523
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089185
Title:
Releasing fails with latest cloud-init on ima
** Merge proposal linked:
https://code.launchpad.net/~r00ta/maas/+git/maas/+merge/478384
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089185
Title:
Releasing fails with latest cloud-init on ima
rtance: Undecided => High
** Changed in: maas/3.5
Importance: Undecided => High
** Changed in: maas/3.4
Milestone: None => 3.5.x
** Changed in: maas/3.5
Milestone: None => 3.4.x
** Changed in: maas
Assignee: (unassigned) => Jacopo Rota (r00ta)
** Changed in: maas
** Tags added: bug-council
** Changed in: maas
Status: Invalid => Triaged
** Changed in: maas
Importance: Undecided => High
** Changed in: maas
Milestone: None => 3.6.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
As per discourse reply https://discourse.maas.io/t/regiond-memory-leak-
and-database-locks-in-maas-3-4-0/9527/2?u=r00ta we need more data to
triage the bug. Such as
- database dump
- logs and full SOS report (will contain confidential info from your machine -
remember to redact everything you don
From the logs there is nothing that indicates this is a MAAS bug. This
is rather a support request, hence I'm closing this
** Changed in: ubuntu
Status: New => Invalid
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Ubun
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075271
Title:
Marking node failed during deployment
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/2075271/+subscri
*** This bug is a duplicate of bug 2058496 ***
https://bugs.launchpad.net/bugs/2058496
This is a duplicate of https://bugs.launchpad.net/maas/+bug/2058496
** This bug has been marked a duplicate of bug 2058496
Commissioning failed during 1st pxe install 24.04
--
You received this bug not
32 matches
Mail list logo
