[rawhide] coreos.ignition.resource.remote failing

[jlebon]

--- FAIL: coreos.ignition.resource.remote (5020.68s)
        harness.go:976: Cluster failed starting machines: machine "b48408dd-d007-48c7-8b11-d96730b10684" failed to start: ssh journalctl failed: ssh: handshake failed: read tcp 127.0.0.1:51882->127.0.0.1:35813: read: connection reset by peer
FAIL, output in tmp/kola

coreos.ignition.resource.remote.zip

[jlebon]

[ 5082.834839] ignition[681]: INFO     : files: createFilesystemsFiles: createFiles: op(3): GET http://rh-kola-fixtures.s3.amazonaws.com/resources/anonymous: attempt #1018
[ 5082.838194] ignition[681]: INFO     : files: createFilesystemsFiles: createFiles: op(3): GET error: Get "http://rh-kola-fixtures.s3.amazonaws.com/resources/anonymous": dial tcp: lookup rh-kola-fixtures.s3.amazonaws.com on [::1]:53: read udp [::1]:48600->[::1]:53: read: connection refused

Looks like DNS issues.

Which is probably because of:

[    6.686355] systemd[1]: Condition check resulted in nm-initrd.service being skipped.
[    6.689165] systemd[1]: Condition check resulted in nm-wait-online-initrd.service being skipped.

Even though we did request networking:

[    8.340871] systemd[1]: Starting CoreOS Enable Network...
[    8.463264] systemd[1]: Finished CoreOS Enable Network.

Which looking at the timestamps... ahh right OK, now that NM is a systemd service, coreos-enable-network.service is running too late.

And... yup coreos/fedora-coreos-config#1068 should fix this then.

[jlebon]

This is fixed now.