Red Hat Bugzilla – Bug 1251878
[origin_platformmanagement_480]Builder and S2I still work after Atomic-enterprise started even add the disabledFeatures config
Last modified: 2016-10-30 18:54:27 EDT
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:
- Web Console
- S2I Builder
Version-Release number of selected component (if applicable):
# atomic-enterprise version
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
Build and S2I work fine
Build and S2I should not work for atomic-enterprise.
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.