Tracker bug for 5.10.7 cfme-openshift-embedded-ansible image
Successfully deployed podified CFME NAME READY STATUS RESTARTS AGE ansible-1-m7ddz 1/1 Running 0 2m cloudforms-0 1/1 Running 0 27m httpd-1-tv79r 1/1 Running 0 27m httpd-configmap-generator-1-gvrxp 1/1 Running 0 17m memcached-1-5k29f 1/1 Running 0 27m postgresql-1-tmnfb 1/1 Running 0 27m [root@epacific-ocp-master-v3 5_10_7_1]# oc rsh cloudforms-0 sh-4.2# cat BUILD 5.10.7.1-20190712211518_68f0bf9 sh-4.2# exit exit [root@epacific-ocp-master-v3 5_10_7_1]# oc rsh httpd-configmap-generator-1-gvrxp sh-4.2# httpd_configmap_generator --help httpd_configmap_generator 0.2.2 - External Authentication Configuration script Usage: httpd_configmap_generator auth_type | update | export [--help | options] supported auth_type: active-directory, ipa, ldap, saml httpd_configmap_generator options are: -V, --version Version of the httpd_configmap_generator command -h, --help Show this message sh-4.2# Verification of the correct tag from the template: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 5m default-scheduler Successfully assigned ansible-1-rpn6r to epacific-ocp-compute2-v3.cmqe.lab.eng.rdu2.redhat.com Normal SuccessfulMountVolume 5m kubelet, epacific-ocp-compute2-v3.cmqe.lab.eng.rdu2.redhat.com MountVolume.SetUp succeeded for volume "cfme-privileged-token-k6k5c" Normal Pulling 5m kubelet, epacific-ocp-compute2-v3.cmqe.lab.eng.rdu2.redhat.com pulling image "registry.access.stage.redhat.com/cloudforms47/cfme-openshift-embedded-ansible:3.5.0-2" Normal Pulled 5m kubelet, epacific-ocp-compute2-v3.cmqe.lab.eng.rdu2.redhat.com Successfully pulled image "registry.access.stage.redhat.com/cloudforms47/cfme-openshift-embedded-ansible:latest" Normal Created 5m kubelet, epacific-ocp-compute2-v3.cmqe.lab.eng.rdu2.redhat.com Created container Normal Started 5m kubelet, epacific-ocp-compute2-v3.cmqe.lab.eng.rdu2.redhat.com Started container [root@epacific-ocp-master-v3 5_10_7_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-2019:1834