Seems to work just fine on 4.4.0-0.nightly-2020-06-29-071755, marking as VERIFIED: mdulko:~/ $ docker run -it registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-06-29-071755 image kuryr-controller Unable to find image 'registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-06-29-071755' locally 4.4.0-0.nightly-2020-06-29-071755: Pulling from ocp/release a03401a44180: Already exists bb0da44cdbce: Already exists e8913ff394b5: Already exists 6c37764d5c15: Pull complete 766e1c1a4e86: Pull complete ac2ada15b5f8: Pull complete Digest: sha256:2dbc394c6007e5a285beb68d74ebc7c55ff5faa863e39008fd2cc16b9ca525d0 Status: Downloaded newer image for registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-06-29-071755 quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a5dc00078f4b78f907f0fb6cb94b7f71984fd6888cade27d0ea6817f00d6d4f3% mdulko:~/ $ docker run -it --entrypoint bash quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a5dc00078f4b78f907f0fb6cb94b7f71984fd6888cade27d0ea6817f00d6d4f3 Unable to find image 'quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a5dc00078f4b78f907f0fb6cb94b7f71984fd6888cade27d0ea6817f00d6d4f3' locally sha256:a5dc00078f4b78f907f0fb6cb94b7f71984fd6888cade27d0ea6817f00d6d4f3: Pulling from openshift-release-dev/ocp-v4.0-art-dev 7f24bdb73d53: Already exists 264aaa453271: Already exists 64c464c381ca: Already exists 489ad58fd7fc: Pull complete Digest: sha256:a5dc00078f4b78f907f0fb6cb94b7f71984fd6888cade27d0ea6817f00d6d4f3 Status: Downloaded newer image for quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a5dc00078f4b78f907f0fb6cb94b7f71984fd6888cade27d0ea6817f00d6d4f3 bash-4.4$ kuryr-k8s-controller --version 4.4.0 bash-4.4$ python3 -m pip freeze | grep kuryr The directory '/var/lib/kuryr/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. kuryr-kubernetes==4.4.0 kuryr-lib==1.1.1
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, 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-2020:2786