Bug 1123363

Summary: Error message is not helpful to user's debug when no node to deploy new head gear.
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: NodeAssignee: Luke Meyer <lmeyer>
Status: CLOSED EOL QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.2.0CC: jokerman, libra-onpremise-devel, mmccomas, rthrashe
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-13 22:17:51 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 Johnny Liu 2014-07-25 12:37:49 UTC
Description of problem:


Version-Release number of selected component (if applicable):
puddle-2-1-2014-07-23

How reproducible:
Always

Steps to Reproduce:
1.Set up env, 1 broker + 2 nodes, and make sure ALLOW_MULTIPLE_HAPROXY_ON_NODE="false" in broker.conf
2.Create a scaling app
3.Sent make-ha rest api to this app, now every node has a head gear.
4.set-multiplier for this app
# oo-admin-ctl-app -l jialiu -a scaphp53app -c set-multiplier --cartridge haproxy-1.4 --multiplier 1
5.Scale up this app.
$ rhc cartridge-scale php-5.3 --min 3 -a scaphp53app

Actual results:
$ rhc cartridge-scale php-5.3 --min 3 -a scaphp53app
This operation will run until the application is at the minimum scale and may take several minutes.
Setting scale range for php-5.3 ... 
Unable to complete the requested operation due to: No nodes available. Please try again and contact support if the issue persists. 
Reference ID: 2e6508ca5f28d503d6d24c4d6bbb4d55

The error message is saying "No nodes available", this error message will confuse user. If user is not familiar with multiplier and node select mechanism, that would bring trouble for debugging.


Expected results:
Similar error message should throw out.
Due to ALLOW_MULTIPLE_HAPROXY_ON_NODE="false", there is no available not to deploy a new haproxy gear.

Additional info:
When I add one more new node to this district, step 5 is pass, a new haproxy gear is created.

Comment 1 Rory Thrasher 2017-01-13 22:17:51 UTC
OpenShift Enterprise v2 has officially reached EoL.  This product is no longer supported and bugs will be closed.

Please look into the replacement enterprise-grade container option, OpenShift Container Platform v3.  https://www.openshift.com/container-platform/

More information can be found here: https://access.redhat.com/support/policy/updates/openshift/