Bug 1136983
Summary: | node.conf config value names have changed | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Luke Meyer <lmeyer> |
Component: | Containers | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1.0 | CC: | adellape, anli, bmeng, dmace, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, pep, perobins |
Target Milestone: | --- | Keywords: | UpcomingRelease |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-origin-node-util-1.22.20.2-1.el6op rubygem-openshift-origin-node-1.23.9.21-1.el6op | Doc Type: | Bug Fix |
Doc Text: |
The default /etc/openshift/node.conf file on node hosts contained gear UID and port settings that are no longer used as described and did not contain the actual settings for those purposes. This made it confusing when trying to change the port range, starting gear UID, or ports per gear. This bug fix updates this default file for new installations to remove the unused options. It also adds notes for options that should not be changed that must remain for historical purposes, and introduces accurate settings (PORTS_PER_USER and PORT_BEGIN) with helpful comments regarding restrictions on changing them. This file on existing installations is unaffected.
|
Story Points: | --- |
Clone Of: | 1051015 | Environment: | |
Last Closed: | 2014-09-11 20:06:58 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: | |||
Bug Depends On: | 1051015 | ||
Bug Blocks: | 1051251 |
Description
Luke Meyer
2014-09-03 18:45:05 UTC
What about UID_BEGIN? Its only use is in another obscure calculation, this time in node/lib/openshift-origin-node/model/frontend_proxy.rb where as with GEAR_MIN_UID the important thing is that it not change. This has never been set in node.conf so it never should be. origin-server cherrypicks: commit 18a380023392daadd0a5c8da96fb8f6ea1b5b08f Author: Luke Meyer lmeyer Date: Sun Aug 31 20:07:29 2014 -0400 node.conf: comments for external port range commit a80d21486a579015e5daea83ad32f8da6c3133cb Author: Luke Meyer lmeyer Date: Wed Sep 3 14:35:56 2014 -0400 oo-accept-node: remove check for unused settings Verify and pass on OSE 2.1.z/2014-09-04.1 1. After update, the node.conf was updated. ->pass 2. oo-accept-node using the uid from broker. -> pass 1) Modify first uid in openshift-origin-msg-broker-mcollective.conf 2) Modify the max uid in broker oo-admin-ctl-district -c remove-capacity -n sgears --size 100 oo-admin-ctl-district -c publish-uids 3) oo-accept-node -v 3. PORT_BEGIN, PORTS_PER_USER take affect. ->pass (Test scenarios for step 3 in comment #7) For step 3, The following scenarios are used to verify PORT_BEGIN, PORTS_PER_USER. 1) set PORT_BEGIN=65531, the oo-iptables-port-proxy will use proxy between 65531 to 65536. September 05 01:52:29 INFO Shell command 'oo-iptables-port-proxy addproxy 65531 "127.10.154.1:8080"' ran. rc=0 out=-I rhc-app-comm 1 -d 127.10.154.1 -p tcp --dport 8080 -j ACCEPT -m comment --comment 65531 September 05 01:52:34 INFO Shell command 'oo-iptables-port-proxy addproxy 65532 "127.10.154.2:8080"' ran. rc=0 out=-I rhc-app-comm 1 -d 127.10.154.2 -p tcp --dport 8080 -j ACCEPT -m comment --comment 65532 S 2) set PORTS_PER_USER=2, the app creation with jbosseap should fail due to no port available. Result: root@node1 node]# cat platform.log|grep "No ports were left available to map" September 05 04:10:59 INFO openshift-agent: request end: action=cartridge_do, requestid=57ad56d6d9b551ff8b9e9f56186f71c4, senderid=broker.ose.com.cn, statuscode=1, data={:time=>nil, :output=>"No ports were left available to map 127.8.146.129:5445: uid=4389", :exitcode=>1, :addtl_params=>nil} Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1183.html |