We are hitting the same problem while booting VM with cloud-init
configuration disk (iso image). Network interface will not configure
itself with dhcp.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/176
Hi Daniel,
Thanks for commenting. I don't believe your issue is the same as this
bug (kernel issue with e1000e driver in the 4.15 kernel). Rather it
appears that you're booting a cloud image outside of a cloud and without
any cloud configuration.
Cloud-init only runs if it detects that it has b
After another edit, namely a symlink of cloud-init.target into the
multi-user.target.wants directory it finally boots up with cloud-init
and everything work as expected.
This is quite a lot of manual work for something that's presented as
`Ready to use`.
I'd like to contribute to the review/QA pr
Creating /etc/systemd/network/default.network with contents:
```
[Match]
Type=en*
[Network]
DHCP=yes
```
is a valid workaround. However, cloud-init is still not run for some
reason, but at least the VM now initializes the NICs.
Are these images tested? are the results somewhere reviewable? It se
I'm also running into this issue..
using today's https://cloud-
images.ubuntu.com/daily/server/bionic/current/bionic-server-cloudimg-
amd64.img - converted into vmdk and using vmxnet3 or e1000 or e1000e
adapters. In any constellation it does not initialize any interfaces or
attempts any DHCP reque
** Attachment added: "Console log"
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1761573/+attachment/5174094/+files/d008743c08a84012b6aca41efbe5b456
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I can no longer deploy Xenial on the same hardware. I see the same
issues as with Bionic (Note that the system PXE boots just fine, loads
the ephemeral env, but gets stuck in the same place).
hostname big-koi hostname big-koi hostname big-koi hostname big-koi hostname
big-koi hostname big-koi IP-
On Thu, Apr 12, 2018 at 4:36 PM, Andres Rodriguez
wrote:
> Ryan,
>
> Maybe I’m missing something but I’m wondering How Will installing Xenial
> and upgrading cloud-initramfs help here when the system boots of the kernel
> and not an ephemeral image/network?
Right, so if Xenial deploys fine, then
Ryan,
Maybe I’m missing something but I’m wondering How Will installing Xenial
and upgrading cloud-initramfs help here when the system boots of the kernel
and not an ephemeral image/network?
On Thu, Apr 12, 2018 at 4:01 PM Ryan Harper <1761...@bugs.launchpad.net>
wrote:
> Hrm, You could install
Hrm, You could install Xenial and then upgrade to bionic's cloud-init
ramfs; but keep the 4.4 kernel. This would allow us to test the
initramfs code vs. the hardware. If 4.4 + cloud-initramfs-tools 0.40
works, then you likely have an issue with the kernel + the e1000e driver
to sort.
--
You rec
The hardware is remote, the only thing I could do is deploy Xenial and
dist-upgrade to Bionic if that helps ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761573
Title:
Network not configured on b
full log
** Attachment added: "maas-1-06.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1761573/+attachment/5112754/+files/maas-1-06.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
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
wrote:
> So it seems that the latest 4.15 kernel in -
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]:
So, what's happening here is the BOOTIF parameter specifies a MAC of a
device, but that device is *not* found; then we see the errors here.
So let's get confirmation that the BOOTIF parameter mac matches with one
or more of the interfaces on the system.
I recreated this same failure by booting a
Possibly related:
https://bugzilla.redhat.com/show_bug.cgi?id=1525523
https://marc.info/?l=linux-kernel&m=151272209903675&w=2
That *should* be in bionic 4.15 ...
and from the log, you're running 4.13.
I suspect kernel bug on e1000e here.
Can you boot with bionic 4.15 kernel and check again?
Also can you provide a list of interfaces and their mac address values?
Maybe the commissioning, lshw output?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761573
Title:
Network not configu
Can you attach the xenial log that boots just fine on the same hardware?
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
** Description changed:
Deploying a machine with Bionic results in networking not configured in
the initramfs, which fails the deployment process.
Deploying Xenial works just fine.
Full log is available in: https://pastebin.ubuntu.com/p/y7nJttSt5x/
- [ 65.435628] async_tx: api i
19 matches
Mail list logo
