Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 907741

Summary: Administrator cannot create a district with a custom gear size until it is included in VALID_GEAR_SIZE
Product: OpenShift Container Platform Reporter: xjia <xjia>
Component: DocumentationAssignee: bmoss
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: low Docs Contact:
Priority: medium    
Version: 1.0.0CC: bleanhar, bmoss, jialiu, jokerman, lcarlon, libra-onpremise-devel, lmeyer, mmccomas, xtian
Target Milestone: ---Keywords: Documentation, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-20 02:39:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description xjia 2013-02-05 07:33:26 UTC
Description of problem:
In the file /etc/openshift/resource_limit.conf, node_profile is "small" by default. As user can change node_profile to other name they want,  so we should let user create the district with the same name

Version-Release number of selected component (if applicable):
http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.1.z/2013-01-30.1/

How reproducible:
100%

Steps to Reproduce:
1.Set node_profile equal "haha" in /etc/openshift/resource_limit.conf
node_profile=haha
2.create a district with "haha" type

  
Actual results:
[root@broker]# oo-admin-ctl-district -p haha -n jia
Node profile must be one of: (small(default)|medium)


Expected results:
Should create successfully

Additional info:

Comment 2 Brenton Leanhardt 2013-02-05 13:55:36 UTC
It would certainly be nice if changing /etc/openshift/resource_limits.conf was the only thing that was needed.  However, currently the oo-admin-crl-district code relies on the VALID_GEAR_SIZES setting in /etc/openshift/broker.conf.  The node profile has to be set there too.

This is getting reworked quite a bit upstream so we'll make sure this gets taken into account there.

Comment 3 Luke Meyer 2013-02-05 16:38:04 UTC
VALID_GEAR_SIZES is mentioned briefly in the admin guide https://access.redhat.com/knowledge/docs/en-US/OpenShift_Enterprise/1/html-single/Administration_Guide/index.html#sect-OpenShift_Enterprise-Administration_Guide-Setting_Default_Gear_Quotas_and_Sizes

It probably deserves a mention in the Deployment Guide section about this as well. https://access.redhat.com/knowledge/docs/en-US/OpenShift_Enterprise/1/html-single/Deployment_Guide/index.html#sect-OpenShift_Enterprise-Deployment_Guide-Continuing_Node_Installation_for_Enterprise-Gear_Profiles

Given the upstream changes for this are indeterminate, I am switching this to a docs bug. The work to be done is:

1. In the admin guide linked above, mention that gear profiles can't be used by admins to create districts, or develoeprs to create applications / gears, until they are listed in VALID_GEAR_SIZES.

2. Likewise in the deploy guide section above.