It still looks like something about the nic isn't working right. Can
you boot something non-network on that hardware and just confirm
that the nic actually works?
On Thu, Apr 12, 2018 at 1:43 PM, Andres Rodriguez
<email address hidden> wrote:
> So it seems that the latest 4.15 kernel in -updates has indeed made a
> difference, however, it hasn't really solve the problem. [1] shows the
> new issue. It doesn't seem to be driver problem and DHCP is working
> fine, provided that otherwise, the machine wouldn't have even gotten to
> this point.
>
> [1]: https://pastebin.canonical.com/p/HjXS85hr4F/
>
> ** Changed in: cloud-initramfs-tools (Ubuntu)
> Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1761573
>
> Title:
> Network not configured on bionic
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1761573/+subscriptions
Can you paste the whole log?
It still looks like something about the nic isn't working right. Can
you boot something non-network on that hardware and just confirm
that the nic actually works?
On Thu, Apr 12, 2018 at 1:43 PM, Andres Rodriguez /pastebin. canonical. com/p/HjXS85hr4 F/ -tools (Ubuntu) /bugs.launchpad .net/bugs/ 1761573 /bugs.launchpad .net/ubuntu/ +source/ cloud-initramfs -tools/ +bug/1761573/ +subscriptions
<email address hidden> wrote:
> So it seems that the latest 4.15 kernel in -updates has indeed made a
> difference, however, it hasn't really solve the problem. [1] shows the
> new issue. It doesn't seem to be driver problem and DHCP is working
> fine, provided that otherwise, the machine wouldn't have even gotten to
> this point.
>
> [1]: https:/
>
> ** Changed in: cloud-initramfs
> Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Network not configured on bionic
>
> To manage notifications about this bug go to:
> https:/