I watched an installation with today's iso (20170321) and it was indicating that it was creating the btrfs filesystem for / when ubiquity stopped and the system rebooted. We're not getting as far as the success_command, so I don't think I can use that to copy logs out. Is there something I can do in an early_command that would work to help get logs out of the installer environment? The automation system we're using (https://code.launchpad.net/utah) uses rsyslog on the system under test after the install completes, I can look into whether it's possible to get it running during the installation. Any other suggestions would be welcome. I can also send the repacked iso or the initrd (with preseed) that we're using to anyone else who might be able to recreate the issue.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673605 Title: Preseeded btrfs installation fails on zesty amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1673605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
