Installing core os on hyper-v fails

[jlpedrosa]

What keywords did you search in tectonic-installer issues before filing this one?

null_resource.etcd_secrets: Still creating...
hyper-v installer

If you have not found any duplicates, delete this section and continue on.

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

Versions

matchbox-v0.7.0
core os: 1745.5.0 => if 1745.6.0 the maxines won't boot after pxe.

Tectonic version

tectonic_1.9.6-tectonic.1

Terraform version (terraform version):

Terraform v0.10.7 (cames with installer)

Platform (aws|azure|openstack|metal|vmware):

metal (hyper-v VMs)

What happened?

Followed the guide: https://coreos.com/tectonic/docs/latest/install/bare-metal/index.html
MatchBox, Installer, worker and master are Hyper-V VMs
Worker and master boots with CoreOs, via PXE -> iPXE -> chain http://matchbox.mycluster:8080/boot.ipxe

but the installer gets stucked at:
null_resource.etcd_secrets: Still creating... (1h0m1s elapsed)

also despite ssh-add works in the installer I can't log in into the machines, it keeps on asking for password, the worker and masters just boots one time but don't get core os installed on disk, so I guess it never copied the ssh keys.

I can't find any error log anywhere to progress.

What you expected to happen?

Core Os to gets installed

Environment

Local PC (Windows 10)
Hyper-V External vritual switch
Matcher and Installer using CentOs 7 latest stable build.

[jlpedrosa]

I've been troubleshooting the other issue (with version 1745.6.0)

When I issue the request:
http://matchbox:8080/ipxe?mac=00%3A15%3A5D%3A0A%3AC9%3A26

kernel /assets/coreos/1745.5.0/coreos_production_pxe.vmlinuz initrd=coreos_production_pxe_image.cpio.gz coreos.config.url=http://matchbox.thearchi.tech:8080/ignition?uuid=${uuid}&mac=${mac:hexhyp} coreos.first_boot=yes console=tty0 console=ttyS0
initrd /assets/coreos/1745.5.0/coreos_production_pxe_image.cpio.gz
boot

So even if I download and add to assets in matchbox 1745.6.0 version, matchbox keeps on trying to push 1745.5.0
Not sure if a given installer can work with only a single version or it's a bug.

JL