in DevOps, System Administration

The current state of OpenShift on Fedora 25

OpenShift has become the most wanted technology of Red Hat. 30% of their current sales are happening because of it. Today, we take a look at using the technology in it’s current state on Fedora 25. Is OpenShift usable without Red Hat support? And if so, what obstacles are there to overcome?

OpenShift 1.5 on Fedora Atomic Host 25

Our mission is setting up OpenShift on an OS with an up-to-date kernel. Additionally, we want rolling updates and as much support from Red Hat (community) as possible. In this setup, we therefore choose fedora atomic host (aka project atomic) over CoreOS. This helpful tutorial posted on project atomic in December 2016, the official documentation as well the the openshift-ansible docs are our guides.

The preferred setup is using the OpenShift ansible recipe. We are not happy with using the devel branch (3.6), so we are going to install the latest stable, which is 3.5 (Origin 1.5). Following the Readme we need to checkout the latest 3.5 tag. As not all tags are listed on github we identify the right one using git tag | sort.

openshift-ansible-3.5.71-1 seems to be the latest, so we are going to use this.

Next, we need an inventory file as stated in this project atomic post. Our config is the same as in this link and yes, we use containerized installation as this is the only available installation method for atomic host.

After setting everything up we run the playbook. And it fails. An issue on github refers to what we encountered and the bad news is: No fix for 3.5 .

Verdict: OpenShift 1.5 on Fedora Atomic Host 25

Our goal was to run OpenShift in a way to allow running it in production with an up-to-date kernel on an OS with a rolling release strategy. The first thing to do when figuring out if something is production ready is trying to install it in the preferred way (according to the docs). My colleagues and I were not able to install OpenShift on Fedora Atomic Host 25 with the official ansible playbook. Next steps would be to manually tamper with the ansible roles, but as the openshift-ansible repo has more than 200.000 lines of code, there really should be a working playbook to use without the need of manual labor for installing OpenShift on Fedora.

To get a complete picture we tried installing the devel version OpenShift 1.6 on Fedora Atomic Host 25 which failed as well. I give you more information about that step below when discussing installing OpenShift on Fedora 25.

OpenShift 1.5 on Fedora 25

Redefining our previous goals to make installation somehow more achievable we skip the self-imposed goal “rolling updates” and stick to Fedora 25. Project Atomic is known for being not the most loved kid around the block, so maybe using a rpmtree distro is not desirable in terms of support.

Steps are the same as above but we do not use containerized hosts as we want to stick to the best support possible, which means using the default / recommended way:

The default method for installing OpenShift Origin on Fedora, CentOS, or RHEL uses RPMs. – Installing on containerized hosts

Let’s take a look of what we are trying to achieve now:

  • Install OpenShift 3.5 on
  • Fedora 25 using the
  • latest openshift-ansible recipe with the
  • RPM package method

We stick to the aforementioned inventory file once again, using the latest openshift-ansible 3.5 tag and disabling the containerization method: containerized=false.

First try fails.

Using the recipe with python2 is not supported on Fedora, so we need yaml for python3. Unfortunately, the recipe for this task seems to be broken:

The pyyaml package is missing although it should be installed by the openshift role. That means we are forced to install the package manually running ansible -i myserver -m command -a "dnf -y install python3-PyYAML" workers. Afterwards, we run the ansible playbook once again, leading to following output:

I did not go into detail above but yes, it is the same error as before.

As this bug has been fixed on devel version OpenShift 1.6, we will try devel again:

OpenShift 1.6 on Fedora 25

Version 1.6 is devel, so let’s prepare ourselves for a bumpy road. However, it is not working at the moment, so what else could go wrong?

Once again we look for the latest release running git tag | sort. We choose openshift-ansible-3.6.68-1 which happens to be the release our nasty bug was fixed in. After checking out the release, we adapt our configuration openshift_release=v1.6.0 and run the playbook one more time:

Alright, this does not seem too bad, let’s fix it by executing ansible -i myserver -m command -a "dnf -y install libcurl-devel" workers

Hopes are high, let’s run the playbook again:

This is where we need to stop our adventure of installing OpenShift on Fedora 25. More information about this bug can be found on github.

Switching to containerization leads to the same error.

Conclusion: OpenShift on Fedora 25

The installer is currently broken. That’s what we did:

  • We chose OpenShift 1.5
  • We chose stable Fedora 25 and stable Fedora Atomic Host 25
  • We used the recommended way of installing OpenShift using openshift-ansible

Errors we encountered:

  • The dependency installation procedure is broken (missing to install python3-pyyaml).
  • We encountered python type conversion errors and
  • python dictionary out of range errors.

Conclusion

Cloud computing is a very lively field of expertise. Several companies claim to have the best possible cloud solution. OpenShift is a highly opinionated kubernetes stack with a high level of complexity when it comes to bringing and holding together all moving parts.

If we take the current state of the openshift-ansible repository in conjunction with Fedora 25, it seems as if OpenShift on Fedora 25 is currently not production ready. This does not necessarily mean that you can’t have a running OpenShift cluster using Fedora 25 in production. It just means that you won’t be able to achieve this goal with the current install procedure and are very likely forced to do a lot of configuring and installing tasks yourself, leading to possible pitfalls during upgrade procedures eventually.