Description of problem: Currently installer only support standalone atomic registry deployment, s2i, web console in cluster will be disabled. Open this bug for requesting to deploy the atomic-registry console to normal OCP clusters by default as well. Here is our discussion: https://github.com/smunilla/openshift-ansible/commit/53d51db6f2da179e867009a0ab0b411ede7d9fe4#commitcomment-18811354 Version-Release number of selected component (if applicable): openshift-ansible-3.3.16-1.git.0.9ed3fd2.el7.noarch How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Upstream docs: [0] https://docs.openshift.org/latest/install_config/install/stand_alone_registry.html [1] https://docs.openshift.org/latest/install_config/install/advanced_install.html#multiple-masters [2] https://docs.openshift.org/latest/install_config/registry/deploy_registry_existing_clusters.html#deploying-the-registry-console
Commit pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/a3ab3d539bb57bc224b3f4457a0bfc68484cf8ee Install Registry by Default Instead of restricting cockpit-ui to Atomic Registry installations, install it by default everywhere. Fixes Bug 1371459
This bug should be already fixed in openshift-ansible-3.3.30-1.git.0.b260e04.el7.noarch, now installer would deploy registry-console by default, once this bug is moved to ON_QA, will verify it.
@Scott, would you mind attach this bug to 3.3.1 installer errata?
Verified this bug with openshift-ansible-3.3.34-1.git.0.5b998bb.el7.noarch, and PASS.
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-2016:2122