Bug 1019190

Summary: Some issues for openshift.sh instllation script.
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: NodeAssignee: Luke Meyer <lmeyer>
Status: CLOSED ERRATA QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0.0CC: bleanhar, libra-onpremise-devel
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: 2013-12-16 09:11:14 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:

Description Johnny Liu 2013-10-15 09:27:53 UTC 
Description of problem:
wget https://raw.github.com/openshift/openshift-extras/enterprise-2.0/enterprise/install-scripts/generic/openshift.sh

Review the code, found the following issues:
1. miss  "|| abort_install" for line 733, and using an incorrect repo name for rhscl channel in line 734.
 731   if need_rhscl_repo
 732   then
 733     rhn-channel --add --channel rhscl-1-x86_64-server-6-rpm --user ${CONF_RHN_REG_NAME} --password ${CONF_RHN_REG_PASS}
 734     echo -e "[jb-ews-2-x86_64-server-6-rpm]\npriority=3\n" >> $RHNPLUGINCONF
 735   fi

2. miss "--save" option for 809 line, and did not set priority for rhscl channel.
 813    if need_rhscl_repo
 814    then
 815      yum-config-manager --enable rhscl-1-for-rhel-6-server-rpms
 816    fi


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Brenton Leanhardt 2013-11-05 19:19:30 UTC 
It looks like the yum configuration code has been refactored recently and that these problems have been addressed.
Comment 3 Johnny Liu 2013-11-07 06:37:16 UTC 
Verified this bug the latest installation script, it is indeed refactored, and the above issue is fixed now.