Luca Bruno

@DirkTheDaring can you please attach subsequent logs entries (i.e. for the whole boot)? In the default configuration, Ignition will keep retrying until it is able to fetch the userdata. Racing...

Additional cloud-specific quirk for OpenStack, coming from https://github.com/openshift/machine-config-operator/pull/964#issuecomment-511109721. As Openstack is not an homogeneous platform and the metadata component is only optional, the static Ignition platform ID is not useful...

We should be now in a better position to tackle this, as at least we have a single network management stack in initramfs in both RHCOS and FCOS (NM with...

For reference, NM lease files do not seem to contain the DHCP option: ``` cat /var/lib/NetworkManager/internal-054597c7-5830-47a8-a54c-77e054ee00aa-eth0.lease # This is private data. Do not parse. ADDRESS=10.1.42.5 ```

To make this ticket easier to find out, this bug currently means that on Azure we have to wait for a timeout: ``` [ 131.232431] afterburn[1103]: WARN Failed to get...

If this a kernel panic, pstore may contain some crash logs. See https://coreos.com/os/docs/latest/collecting-crash-logs.html and let us know if there is anything relevant there. I didn't spot anything interesting from your...

We have seen reports of several hiccups specific to m5 instances (lockups, long pauses): https://github.com/coreos/bugs/issues/2326. Is this NVMe attach failure specific to this kind of instances? If so, you may...

@Quentin-M it looks like kernels 4.16 and 4.17 are getting a lot of NVMe-related stability/correctness patches (I'm specifically looking at [this](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/nvme/host/pci.c?h=v4.16.2&id=2b1b7e784a63f5ded4dda804e05e3f34b3880b25) and [this](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host?id=bb06ec31452fb2da1594f88035c2ecea4e0652f4), but I'm not very familiar with NVMe)...

@Quentin-M alpha 1758.0.0 is out with kernel 4.16.3, did you have a chance to try that yet?

@Quentin-M I would suggest to check 1828.0.0, which is the first release shipping with 4.17. That should hopefully bring stability to the driver. If not, I would suggest reporting this...