Bug 1021380 - There is no exit code when adding login to domain meets max member limit
Summary: There is no exit code when adding login to domain meets max member limit
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Master
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Ravi Sankar
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-21 08:10 UTC by Meng Bo
Modified: 2015-05-15 00:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-24 03:25:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Meng Bo 2013-10-21 08:10:08 UTC
Description of problem:
Modify the max_members_per_resource to 3 in development.rb file and restart broker service.
Try to add more than 3 members to the domain via RESTAPI.

It will return proper message but do not have exit code.

  <messages>
    <message>
      <severity>error</severity>
      <text>The members could not be added due to validation errors.</text>
      <exit-code nil="true"></exit-code>
      <field nil="true"></field>
      <index nil="true"></index>
    </message>
  </messages>


Version-Release number of selected component (if applicable):
devenv_3921

How reproducible:
always

Steps to Reproduce:
1. Set the max_members_per_resource
2. Restart broker and clear broker cache
3. Try to add member to the domain more than the limit

Actual results:
No exit code for the operation.

Expected results:
Should have exit code.

Additional info:

Comment 2 Dan McPherson 2013-11-11 23:45:33 UTC
exit code should be 222 and the message should be more detailed now.

https://github.com/openshift/origin-server/pull/4166

Comment 4 Meng Bo 2013-11-12 10:18:19 UTC
  <messages>
    <message>
      <severity>error</severity>
      <text>You are limited to 2 members per domain</text>
      <exit-code>222</exit-code>
      <field>members</field>
      <index nil="true"></index>
    </message>
  </messages>


Issue has been fixed on devenv_4022.


Note You need to log in before you can comment on or make changes to this bug.