Steps to reproduce: 1. create a project template to use as default 2. configure master to use project template as default 3. create project using "oadm new-project" Default project template is ignored... or, at least, quota and limits sections are ignored. Template for reference attached. atomic-openshift-3.0.2.901-0.git.61.568adb6.el7aos.x86_64 atomic-openshift-clients-3.0.2.901-0.git.61.568adb6.el7aos.x86_64 atomic-openshift-master-3.0.2.901-0.git.61.568adb6.el7aos.x86_64 atomic-openshift-node-3.0.2.901-0.git.61.568adb6.el7aos.x86_64 atomic-openshift-sdn-ovs-3.0.2.901-0.git.61.568adb6.el7aos.x86_64 tuned-profiles-atomic-openshift-node-3.0.2.901-0.git.61.568adb6.el7aos.x86_64
Created attachment 1084539 [details] default project template with quota/limit
So the suggestion here is that this behavior exists because "oadm new-project" doesn't involve a projectRequest -- and the defined "default" is for projectRequests. However, this is an unexpected user experience. "oadm new-project" should probably inherit the default template, or allow to specify a template explicitly. Having to use "oc process" to create a default-looking project for a user seems strange and cumbersome.
This bug has been identified as a dated (created more than 3 months ago) bug. This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, as it is currently not part of the products immediate priorities. Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.