Version: 2.0.0-SNAPSHOT-2020-07-02-15-26-48 Cluster version is 4.5.0-rc.4 Steps to reproduce: Attempt to create a baremetal cluster Result: The baremetal assets user and password in the generated <clustername>-install-config secret aren't set and cluster deployment fails early with the following log: REDACTED LINE OF OUTPUT time="2020-07-02T20:22:10Z" level=error msg="error after waiting for command completion" error="exit status 1" installID=bhqf4kw7 time="2020-07-02T20:22:10Z" level=error msg="error generating installer assets" error="exit status 1" installID=bhqf4kw7 time="2020-07-02T20:22:10Z" level=info msg="reading installer log" installID=bhqf4kw7 time="2020-07-02T20:22:10Z" level=info msg="saving installer output" installID=bhqf4kw7 time="2020-07-02T20:22:10Z" level=debug msg="installer console log: REDACTED LINE OF OUTPUT\n" installID=bhqf4kw7 time="2020-07-02T20:22:10Z" level=info msg="updating clusterprovision" installID=bhqf4kw7 time="2020-07-02T20:22:10Z" level=fatal msg="runtime error" error="exit status 1" If we disable the log redaction, we'll see: time="2020-07-02T20:50:41Z" level=debug msg="installer console log: level=fatal msg=\"failed to fetch Master Machines: failed to load asset \\\"Install Config\\\": invalid \\\"install-config.yaml\\\" file: [platform.baremetal.hosts[0].BMC.Username: Required value: missing Username, platform.baremetal.hosts[0].BMC.Password: Required value: missing Password, platform.baremetal.hosts[1].BMC.Username: Required value: missing Username, platform.baremetal.hosts[1].BMC.Password: Required value: missing Password, platform.baremetal.hosts[2].BMC.Username: Required value: missing Username, platform.baremetal.hosts[2].BMC.Password: Required value: missing Password, platform.baremetal.hosts[3].BMC.Username: Required value: missing Username, platform.baremetal.hosts[3].BMC.Password: Required value: missing Password, platform.baremetal.hosts[4].BMC.Username: Required value: missing Username, platform.baremetal.hosts[4].BMC.Password: Required value: missing Password]\"\n" installID=h2ssqpn4 time="2020-07-02T20:50:41Z" level=info msg="updating clusterprovision" installID=h2ssqpn4 time="2020-07-02T20:50:41Z" level=fatal msg="runtime error" error="exit status 1 Workaround: After filling all the fields, edit the generated yaml and set username and password to their actual values and click on "create cluster".
*** Bug 1853605 has been marked as a duplicate of this bug. ***
This seem to work fine with snapshot: 2.0.0-SNAPSHOT-2020-07-07-22-44-12
Verified based on comment #2
This was delivered in ACM 2.0. I am reconciling our books.