OKD 4.19 IPI using internal Quay registry - Resulting in failure during OVA deployment

[linuxcube]

Hi Team,
After finding the @bsherper youtube channel, I decided to do some testing on OKD. It has been a wild week trying to get OKD deploy using IPI, everything appears to result on failure....I have tried 4.17, 4.18 and now 4.19, all resulting in diferent failures during either the bootstrap process or during the VM deployment.

I have a basic VMware setup ( perhaps no too basic since I am using VDS)..haha.

I have download the oc from the github repo, I have recreated the open-shift installer base on the code hosted on my internal repo.

When I do the openshift deploy and append the install-config with all my VMware parameters, I see the installer going and in the VMware console I can see the ova getting upload, but then I get the following message in my terminal and things end abrutly.

ERROR failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to run cluster api system: failed to run local control plane: failed to unpack envtest binaries: failed to extract "cluster-api/kube-apiserver": open cluster-api/kube-apiserver: text file busy

Specs:
VMware 7.x

I am using the pullsecret of my registry as well as the ImageContentSources parameters as suggested by @bsherper, I am running out of steam on this one, any clues or pointers?

[linuxcube]

Team, after fighting with this OKD thing for last three days, I finally was able to deploy 4.19 sub 6....I thnk I made a lot of mistakes since I tried 4.17 and 4.18 as well, I will try to redeploy those to ensure those are also deployable. I am happy since I did my first deployment using my own self hosted quay, for some reason I was not able to get it deploy using harbor, perhaps more mistakes I made on my own, I will have to do some more testing since I like harbor a lot, but quay is interesting and it seems very easy* to manage since it runs in a container. Anyways, false alarm on this post.

Below find my first deployment of 4.19 sub 6...I could not have done this without all the help from the U-tube channel of @bsherper, his content related to okd and OCP is amazing. Thank you all for the support.

[linuxcube]

Hi Team, Quick update on 4.17.0 sub 3 rollout via IPI, it works fine but I did face some challenges where the bootstrap would timout after the 15 minutes preset. I had to use the wait for bootstrap and wait for installation runs in order to see where bookstrap was in terms of execution, ultimately it completed but it took longer than I expected, so famous last words be patient with bootstrap. Follow the basics of checking crio and the co via bootstrap CLI using ssh, the co status would give clues on the status. Overall it finish fine see reference below:

[linuxcube]

Hi Team, just completed the OKD 4.18.0 sub 10, everything was deploy via IPI under vmware....working well except that bootstrap didnt get kill/remove after handover to control plan master noder. No issue, I just shut it down and delete manually, but I guess this is a bug in the 4.18 installer/deployment. All in all, things are deploying well with IPI under vmware with minor things to look into. See reference below.

[shank15217]

Why don't you actually link his site instead of saying @bsherper so others can follow it.