** Changed in: subiquity
Status: Fix Committed => 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/1865027
Title:
focal-arm64 install fails. No space left on device on /target
To
For the record: curtin did leak efibootmgr calls in some cases, the bug
has been by this curtin commit:
https://git.launchpad.net/curtin/commit/?id=0fed7d68b8f5863cd4a872828608db9f568cc271
This subiquity commit pulls in the fix and drops the staging of
efibootmgr:
Fixes are committed to edge, will be published to stable soon. Not sure
of actual root cause, but not reproducing anymore.
** Changed in: probert (Ubuntu)
Status: Incomplete => Invalid
** Changed in: curtin
Status: Incomplete => Invalid
--
You received this bug notification
I had a longer discussion with Ryan today on the "efibootmgr not found"
issue that we hit after getting rid of the subiquity crash which caused
/target to be unmounted. The conclusion is that curtin should *not* need
efibootmgr to be present in the ephemeral system after all, so we didn't
actually
** Changed in: subiquity
Status: Confirmed => Fix Committed
** Changed in: curtin
Status: New => Incomplete
** Changed in: probert (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Install succeeds with subiquity edge with
https://github.com/CanonicalLtd/subiquity/commit/f929f565fd59f11b7b2d60f2492490d4a3c8f9d0
merged in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865027
The 11/SEGV crash doesn't happen with edge, but the install still fails.
Crash file attached.
** Attachment added: "1585813849.066230536.install_fail.crash"
https://bugs.launchpad.net/subiquity/+bug/1865027/+attachment/5344722/+files/1585813849.066230536.install_fail.crash
--
You received
In any case, can someone who can reproduce this try with edge?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865027
Title:
focal-arm64 install fails. No space left on device on /target
To manage
It would be amazingly strange, but it's possible that
https://github.com/CanonicalLtd/subiquity/pull/670 will make the crash
go away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865027
Title:
Ah wait, subiquity is segfaulting when curtin is in net-meta auto. That
makes me very much suspect the crash is inside probert. Did libnl3
change recently?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So I think Paride is more or less right in #10: One of the subiquities
starts the install. One of the subiquities then segfaults (doesn't
matter which one). Systemd restarts this subiquity, which then unmounts
/target, so the subiquity running the install just copies
filesystem.squashfs to RAM and
For what it is worth apport has some code to prevent this from
happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865027
Title:
focal-arm64 install fails. No space left on device on /target
** Also affects: probert (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865027
Title:
focal-arm64 install fails. No space left on device on
13 matches
Mail list logo
