"ibi-ignition.json" created by ib-cli contains unexpected data

[pamoedom]

Installation failure:

Displaying logs from failed units: sysroot.mount
ignition-fetch-offline.service
Apr 02 09:03:14 systemd[1]: Mounting /sysroot...
Apr 02 09:03:14 mount[853]: mount: /sysroot: failed to setup loop device for /root.squashfs.
Apr 02 09:03:15 systemd[1]: sysroot.mount: Mount process exited, code=exited, status=32/n/a
Apr 02 09:03:15 systemd[1]: sysroot.mount: Failed with result 'exit-code'.
Apr 02 09:03:15 systemd[1]: Failed to mount /sysroot.
Apr 02 09:03:14 ignition[840]: reading system config file "/usr/lib/ignition/user.ign"
Apr 02 09:03:14 ignition[840]: parsing config with SHA512: ad427c9776161d9eb236352ee41bde4b7c807df00e248a117a735d52e256f88ba4a4723d1860a8af00490d476326359e81594857a8fbfcd295f45123cdf7ced0
Apr 02 09:03:14 ignition[840]: error at line 1 col 2: invalid character 'T' looking for beginning of value
Apr 02 09:03:14 ignition[840]: failed to fetch config: config is not valid
Apr 02 09:03:14 ignition[840]: failed to acquire config: config is not valid
Apr 02 09:03:14 ignition[840]: Ignition failed: config is not valid
Apr 02 09:03:14 systemd[1]: ignition-fetch-offline.service: Main process exited, code=exited, status=1/FAILURE
Apr 02 09:03:14 systemd[1]: ignition-fetch-offline.service: Failed with result 'exit-code'.
Apr 02 09:03:14 systemd[1]: Failed to start Ignition (fetch-offline).
Apr 02 09:03:14 systemd[1]: ignition-fetch-offline.service: Triggering OnFailure= dependencies.

Ignition header with unexpected content:

$ head ibi-ignition.json 
Trying to pull quay.io/coreos/butane:release...
Getting image source signatures
Copying blob sha256:ca6ff2c3ecc46249e52c6e55cb2180a62e4550cda750ce9ebf6eb9c35bfa94da
Copying blob sha256:3096d971ecfe41dce90db4e2106eed33ac150c6e6539de82201175f38ca5f6bd
Copying config sha256:f6ad36efa54144abafc015d86ae162da47bb6a4dd8ed15367a3dd320f254aba7
Writing manifest to image destination
{
  "ignition": {
    "version": "3.4.0"
  },

[leo8a]

/cc @eranco74 @tsorya

[pamoedom]

FWIW, please note that the ib-cli binary used in this case was built using the workarounds mentioned here to get rid of some issues.

[pamoedom]

Extra note FYI, this problem only happened the first time, when the quay.io/coreos/butane needed to be downloaded, subsequent executions are not showing the issue within the ibi-ignition.json file.