Hide Forgot
deployment_subtype=registry always sets disabledFeatures Description of problem: deployment_subtype=registry always sets disabledFeatures Version-Release number of selected component (if applicable): atomic-openshift-utils-3.3.28-1.git.0.762256b.el7.noarch How reproducible: Steps to Reproduce: 1. Install master and registry with all-in-one as desribed in https://docs.openshift.com/container-platform/3.3/install_config/install/stand_alone_registry.html#registry-advanced-installation Actual results: master-config.yaml always has disabledFeatures and doesn't allow webconsole access. [root@knakayam-standalone-registry ~]# cat /etc/origin/master/master-config.yaml |grep disable disabledFeatures: ["Builder", "S2IBuilder", "WebConsole"] Documentation described all-in-one installation, so it should not be set by default. Expected results: When users install registry with master api (console), it should not set disabledFeatures.
This is by design, pls refer to https://github.com/smunilla/openshift-ansible/commit/53d51db6f2da179e867009a0ab0b411ede7d9fe4#commitcomment-18787097. In the coming release, this issue will be fixed.
> In the coming release, this issue will be fixed. Could you please share the PR link with us?
This should be a dup with 1371459, pls go though that bug to looking for PR.
Your report in bug#1371459 is same with this ticket. However, latest code still implements the disable settings as below: https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_facts/library/openshift_facts.py#L803-L805 But you meant that deployment_subtype=registry will never set disabledFeatures after the fix in bug#1371459 ?
Ah, my previous comments maybe confuse you. Sorry for that. To be more clear: When deployment_subtype=registry is set, that means user will deploy a standalone registry on purpose, so it is by design to set disabledFeatures. If you want a normal cluster (without disabledFeatures) + atomic registry, what you need do is remove "deployment_subtype=registry" from your inventory, because atomic-registry will be deployed in each installation by default, once bug#1371459 is fixed.
Thank you for the clarification. Now, I understand that what the all-in-one means in the documentation... However, in the first place, is this the best design which engineering team considered to install standalone registry? I feel that it is a pain that users need to install master and node just only for the standalone registry. [1] https://docs.openshift.com/container-platform/3.3/install_config/install/stand_alone_registry.html#registry-supported-system-topologies
(In reply to Kenjiro Nakayama from comment #6) > However, in the first place, is this the best design which engineering team > considered to install standalone registry? I feel that it is a pain that > users need to install master and node just only for the standalone registry. There is some user only need a standalone registry after install master and nodes as a cluster, for making it works like dockerhub. This is my guess. To resolve your pain, I opened BZ#1371459.
> To resolve your pain, I opened BZ#1371459. Sorry, BZ#1371459 is the fix to deploy registry console during OpenShift Master, isn't it? I don't think the BZ#1371459 solve the pain. I meant that the most of users who use registry as standalone, I believe that they don't want to install it with OpenShift (both master and node).
(In reply to Kenjiro Nakayama from comment #8) > > To resolve your pain, I opened BZ#1371459. > > Sorry, BZ#1371459 is the fix to deploy registry console during OpenShift > Master, isn't it? I don't think the BZ#1371459 solve the pain. > > I meant that the most of users who use registry as standalone, I believe > that they don't want to install it with OpenShift (both master and node). Maybe your understanding to ALL-IN-ONE is not right, ALL-IN-ONE is meaning install master + node on one host, in this cluster, only have 1 host. registry console is only a pod deployed onto the cluster by installer. So BZ#1371459 is indeed resolve your issue, regardless of deploying registry console onto Master or master + node cluster, once you trigger installation without deployment_subtype=registry, you will always get a normal cluster which allow you access web console and a working registry console together.
> Maybe your understanding to ALL-IN-ONE is not right, ALL-IN-ONE is meaning install master + node on one host, in this cluster, only have 1 host. That's the my understanding. OK, to clarify my thoughts, what do you answer if the users asked that "how to install standalone registry?" You will answer that installing registry with OpenShift master+node? Anyway, this discussion is different from this bz report, so we should discuss it somewhere else.
PM requested that the registry sub type only deploys the registry and that other features are disabled.