+++ This bug was initially created as a clone of Bug #1779791 +++ +++ This bug was initially created as a clone of Bug #1779740 +++ ``` * module.compute.data.ignition_config.ign[0]: data.ignition_config.ign.0: No valid JSON found, make sure you're using .rendered and not .id: invalid character 'c' after top-level value * module.control_plane.data.ignition_config.ign[2]: data.ignition_config.ign.2: No valid JSON found, make sure you're using .rendered and not .id: invalid character 'b' after top-level value * module.control_plane.data.ignition_config.ign[1]: data.ignition_config.ign.1: No valid JSON found, make sure you're using .rendered and not .id: invalid character 'b' in literal false (expecting 'a') * module.bootstrap.data.ignition_config.ign: data.ignition_config.ign: No valid JSON found, make sure you're using .rendered and not .id: invalid character 'b' after top-level value * module.compute.data.ignition_config.ign[2]: data.ignition_config.ign.2: No valid JSON found, make sure you're using .rendered and not .id: invalid character 'c' looking for beginning of value * module.control_plane.data.ignition_config.ign[0]: data.ignition_config.ign.0: No valid JSON found, make sure you're using .rendered and not .id: invalid character 'c' after top-level value * module.compute.data.ignition_config.ign[1]: data.ignition_config.ign.1: No valid JSON found, make sure you're using .rendered and not .id: invalid character 'e' after top-level value ``` https://prow.svc.ci.openshift.org/log?job=release-openshift-ocp-installer-e2e-vsphere-upi-4.3&id=438 https://prow.svc.ci.openshift.org/log?job=release-openshift-ocp-installer-e2e-vsphere-upi-serial-4.3&id=439 --- Additional comment from Jonathan Lebon on 2019-12-04 15:51:53 UTC --- Not sure if this is related to the other Vsphere UPI 4.3 failures we're seeing: https://bugzilla.redhat.com/show_bug.cgi?id=1752409. The failure mode is different, so I made it a different issue.
Not an installer issue, update terraform script and run installation succeed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:4181