This message was deleted.

ok looks like it is. Does anyone know how to remove the "console=ttyS0" from the grub menu if I am doing install via pxe boot? here is the current pxe script I and passing to the install, #!ipxe kernel harvester-v1.1.1-vmlinuz-amd64 ip=dhcp vlan=eno1.3020:eno1 net.ifnames=1 rd.cos.disable rd.noverifyssl console=tty1 root=live:http://test/harvester/harvester-v1.1.1-rootfs-amd64.squashfs harvester.install.automatic=true harvester.install.config_url=http://test/harvester/harvester-config.yaml initrd harvester-v1.1.1-initrd-amd64 boot

just confirming you are installing 1.1.1?

Yes, I also tried 1.2.0 today. I'll try the adjustments

and all versions get stuck here?

I've done 1.1.1 1.1.2 and 1.20 and yes they get stuck here.

Did you specify /dev/nvme0 as both "device" and "data_disk" in the configuration YAML?

they are separate, here is my config file

scheme_version: 1
token: cooltoken # Replace with a desired token
os:
  hostname: harvester-local # Set a hostname. This can be omitted if DHCP server offers hostnames
  password: testpwd
  ntp_servers:
  - 10.15.20.254
  dnsnameservers:
  - 8.8.8.8
install:
  iso_url: <http://localserver/harvester/harvester-v1.2.0-amd64.iso>
  debug: true
  mode: create
  managementinterface:
    interfaces:
    - name: eno1
    method: static
    ip: 10.66.1.103
    subnetmask: 255.255.255.0
    gateway: 10.66.1.1
    defaultroute: true
    bondoptions:
      miimon: "100"
      mode: active-backup
    mtu: 9000
    vlanid: 3500
  vip: 10.66.1.104
#  viphwaddr: ""
  vipmode: static
  forceefi: false
  device: /dev/nvme1n1
  silent: false
  poweroff: false
  noformat: false
  debug: false
  tty: tty1
  forcegpt: true
  forcembr: false
  datadisk: /dev/nvme0n1
  tty: tty1   # For machines without a VGA console

Sorry, nothing else is standing out to me.

installer has gone past validation phase

Just want to update incase anyone stumbles into this, So the issue was my DHCP server was not providing a default route to the machine as it was running harvester installer. Kubernetes needs a default route (even if it isn't functional) to install properly. So kubernetes never installed and the installer was hanging. Providing default route with dhcp fixed the issue and it installs successfully 😄

touchy touchy. I ran into that situation after a reboot, but didn't think it would affect the install. if the system doesn't have a default route, kubernetes won't start. So instead of deleting the default route on the mgmt-br interface, I set the route metric to 200 since my default goes out another interface that is separately managed.