This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "debug_md_device.txt"
https://bugs.launchpad.net/curtin/+bug/1618429/+attachment/4809253/+files/debug_md_device.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618429
If we can get the full installation log with the same error, please open
up a new bug against curtin. While the error mentioned in comment #30
is mdadm related, this bug addressed errors during mdadm scan of
previous disks and the issue in comment #30 is something else.
--
You received this bug
On Wed, Jan 18, 2017 at 8:43 AM, Ante Karamatić <
ante.karama...@canonical.com> wrote:
> Yes, failures are consistent and happen even after 'erase disks' is enabled
> in MAAS. They also happen on all nodes. I'm afraid I can't get any more
> logs than this. This is all that MAAS can capture in
Yes, failures are consistent and happen even after 'erase disks' is enabled
in MAAS. They also happen on all nodes. I'm afraid I can't get any more
logs than this. This is all that MAAS can capture in this environment.
On Wed, Jan 18, 2017 at 3:00 PM Ryan Harper <1618...@bugs.launchpad.net>
Is it possible to include the entire installation.log?
Do repeat deploys to the same node and same configuration fail
consistently?
On Wed, Jan 18, 2017 at 6:50 AM, Ante Karamatić <
ante.karama...@canonical.com> wrote:
> ** Attachment added: "installation.log"
>
** Attachment added: "installation.log"
https://bugs.launchpad.net/curtin/+bug/1618429/+attachment/4805810/+files/installation.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618429
Title:
I'm not sure this is fixed. We are still seeing problems:
MAAS' curtin version is 0.1.0~bzr425-0ubuntu1~16.04.1. Installation log
and curtin-config (obfuscated) is provided as attachments.
** Attachment added: "curtin-config.txt"
This bug was fixed in the package curtin - 0.1.0~bzr425-0ubuntu1~16.04.1
---
curtin (0.1.0~bzr425-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
[ Scott Moser ]
* debian/new-upstream-snapshot: add writing of debian changelog entries.
[ Ryan Harper ]
* New upstream
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618429
Title:
Curtin doesn't clean up previous MD configuration
To manage
I'd like to add some comments for the SRU verification.
This issue was discovered on a customer's system which is not currently
available for verification. Analyzing the error code in the original
bug was when mdadm assemble was called on an array that was incomplete
(some members not available)
Added José Pekkarinen, in hopes able to verify the xenial-proposed fix
for this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618429
Title:
Curtin doesn't clean up previous MD configuration
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Fix Released
** Changed in: curtin (Ubuntu Xenial)
Status: New => Fix
13 matches
Mail list logo
