Description of problem: I corrupted the pull secret when I created the cluster, by adding random characters to the different blobs in it. Installation failed with: Cluster installation failed Generating kubeconfig files ignition-generator-140df53a-0faa-4083-8a96-ca80f43b9305-1600257 failed for cluster 140df53a-0faa-4083-8a96-ca80f43b9305: job <ignition-generator-140df53a-0faa-4083-8a96-ca80f43b9305-1600257> failed <3> times. Reset the installation process to return to the configuration and try again. Some hosts may need to be re-registered by rebooting into the Discovery ISO. When I clicked on "Download Installation Logs" I got: Could not download cluster installation logs. No log files were found Version-Release number of selected component (if applicable): Staging environment from Sep. 16 How reproducible: 100% Steps to Reproduce: 1. Create a new cluster and change the pull secret so it's not valid, for example by adding random characters to the different blobs 2. Run a cluster installation Actual results: The error message is uninformative Expected results: More details on what went wrong, so it'll be easy to figure out that the pull secret is not right
We already have a wiremock defined so pull secret can probably be validated when defined.
https://github.com/openshift/assisted-service/blob/master/internal/cluster/validations/validations.go#L123-L141
Duplication with https://issues.redhat.com/browse/MGMT-2137
Verified ======== Staging v1.0.9.4
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 (OpenShift Container Platform 4.6.43 bug fix update), 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-2021:3197