search

IBM / Ansible-OpenShift-Provisioning

Automate the deployment of Red Hat OpenShift Container Platform on IBM zSystems (s390x). Automated User-Provisoned Infrastructure (UPI) setup using Kernel-based Virtual Machine (KVM).
https://ibm.github.io/Ansible-OpenShift-Provisioning/
MIT License
20 stars 44 forks source link

Openshift installer tarball for rhel 9 extracts to `openshift-install-fips` #305

Open mohammedzee1000 opened 3 months ago

mohammedzee1000 commented 3 months ago

From OCP 4.16 onwards a new separate installer tarball is added for rhel 9 (openshift-install-rhel9-s390x.tar.gz). The normal binary is for rhel 8.

Downloading this and extracting it results in installer binary called openshift-install-fips instead of openshift-install. This will cause AOP install to fail as it wont find openshift-install binary.

❯ wget https://mirror.openshift.com/pub/openshift-v4/s390x/clients/ocp/4.16.5/openshift-install-rhel9-s390x.tar.gz
❯ tar -xzf openshift-install-rhel9-s390x.tar.gz
❯ ls
 openshift-install-fips   openshift-install-rhel9-s390x.tar.gz
mohammedzee1000 commented 3 months ago

A possible workaround for this is to mirror the installer and oc client tarballs You download, extract, and rename the installer binary (see below), then recreate the tarball, and host both the client tarball and newly created installer tarball in a location on a file server, and provide that URL to clients_download_url

FN=`ls openshift-install*`
if [[ $FN != "openshift-install" ]]; then
    mv $FN openshift-install
fi
tar -czf openshift-install-linux.tar.gz openshift-install

A possible fix would be to detect the binary name after extraction and rename it in shell, this can be done as above (except the tarball recreation)

Of course, we would do something similar in Ansible.

mohammedzee1000 commented 3 months ago

I think this affects any rhel 9 bastion based install