Description of problem:

Install of kata-operator fails

Version-Release number of selected component (if applicable):

openshift version 4.6.0-0.nightly-2020-09-10-121352

kata-operator version https://github.com/openshift/kata-operator/commit/798a74f79104bc65502f6d2060d93205e294b8fb

How reproducible:

Everytime

Steps to Reproduce:
1. run 'deploy/deploy.sh'
2. run 'oc apply -f deploy/crds/kataconfiguration.openshift.io_v1alpha1_kataconfig_cr.yaml'
3.

Actual results:

Logs from kata-operator-daemon-install pod:
W0910 19:22:43.922704  277285 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
/usr/bin/mkdir -p /host/opt/kata-install
/usr/bin/mkdir -p /etc/yum.repos.d/
/usr/bin/cp -f /usr/local/kata/latest/packages.repo /etc/yum.repos.d/
/usr/bin/cp -a /usr/local/kata/latest/packages /opt/kata-install/packages
Checking out tree 3fc6b98...done
Enabled rpm-md repositories: packages
rpm-md repo 'packages' (cached); generated: 2020-07-21T11:38:31Z
Importing rpm-md...done
Resolving dependencies...done
error: Base packages would be removed: glusterfs-fuse-6.0-37.el8.x86_64
/bin/bash -c /usr/bin/rpm-ostree install --idempotent kata-runtime kata-osbuilder
2020/09/10 19:22:56 exit status 1

Expected results:

operator in install correctly with no errros

Additional info:

This is not a new bug, and is supposed to be fix through other changes.  Logging here to keep track of it.