I am seeing the same thing on the non-arm version as well. There seems to be a hang if there is no IP on a detected Ethernet interface. I get to "Reached target Basic System" and then sit there for ~150 seconds at which point I get dracut messages. If I plug in an ethernet cable, the system boots cleanly. When the system does boot correctly, it looks like the box is doing a double lease:

192.168.1.75 00:01:c0:20:b2:ea 2018/11/11 22:03:44 2018/11/12 00:03:44 online active
192.168.1.74 00:01:c0:20:b2:ea 2018/11/11 22:03:33 2018/11/12 00:03:33 online active

I was able to cross verify this with a virtual instance by disconnecting the NIC and the same thing happens. I am using the 11/06 build.

Dave

On Wed, Nov 7, 2018 at 10:09 AM Peter Robinson <pbrobinson@gmail.com> wrote:

On Tue, Nov 6, 2018 at 2:17 PM Paul Kennedy <paul@the-kennedys.me.uk> wrote:
>
> About 15 seconds into booting the ostree image:
> libphy: lan78xx-mdiobus: probed
> usbcore: registered new interface driver lan78xx
> IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>
> hmmm - maybe I need to disable ipv6?

No, IPv6 should be fine, looking at dracut and the error message
originates from the 35network-legacy which we don't even ship. We'll
need to dig into why that module is even getting put into the initrd.

Peter
_______________________________________________
IoT mailing list -- iot@lists.fedoraproject.org
To unsubscribe send an email to iot-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org