Description of problem: After start atomic-enterprise, the builder and S2I still work, and even add the following config to master-config.yaml, builder and S2I still work: disabledFeatures: - Web Console - Builder - S2I Builder Version-Release number of selected component (if applicable): devenv-fedora_2129 # atomic-enterprise version atomic-enterprise v1.0.4-112-g1954a4b kubernetes v1.0.0 How reproducible: always Steps to Reproduce: 1. Start atomic-enterprise atomic-enterprise start --master-config=openshift.local.config/master/master-config.yaml --node-config=openshift.local.config/node-ip-10-11-200-112/node-config.yaml 2. Create application which need S2I build 3. Check if the build can work or not Actual results: Build and S2I work fine Expected results: Build and S2I should not work for atomic-enterprise. Additional info:
Fixed upstream: - https://github.com/openshift/origin/pull/4046 - https://github.com/openshift/origin/pull/4115
Now the Atomic Enterprise Platform is using atomic-openshift-master/node service just as OpenShift Enterprise, the related feature would be disabled according to the deployment_type when installing the environment. Move the bug to VERIFIED for the AEP could installed successfully and WebConsole/Builder/S2I Builder is disabled by default.