ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher White (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-4015) os_type_check.sh & CentOS 6.5
Date Sat, 07 Dec 2013 20:24:35 GMT
Christopher White created AMBARI-4015:
-----------------------------------------

             Summary: os_type_check.sh & CentOS 6.5
                 Key: AMBARI-4015
                 URL: https://issues.apache.org/jira/browse/AMBARI-4015
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 1.4.1
         Environment: CentOS 6.5
            Reporter: Christopher White
            Priority: Trivial


The version checking logic in {{ambari-server/src/main/python/os_type_check.sh}} appears to
be flawed, especially for CentOS 6.5 - When trying to install Ambari I see the following errors
during the installation phase of a node:

{code}
Cluster primary OS type is redhat6 and local OS type is centos5
Local OS is not compatible with cluster primary OS. Please perform manual bootstrap on this
host
{code}

This is assume is because of these lines in {{os_type_check.sh}}:

{code}
if [ -f "/etc/centos-release" ]
then
  grep -qE "${pattern}6 etc/centos-release && current_os=$C6
  grep -qE "${pattern}5 etc/centos-release && current_os=$C5
{code}

The problem appears to be that centos 6.5 matches for both statements, meaning the final value
of current_os is $C5 (centos5)

Here's a short bash session to demonstrate this on my CentOS 6.5 VM:

{code}
[root@ambari-server-vm ~] # cat /etc/centos-release
CentOS release 6.5 (Final)
[root@ambari-server-vm ~] # grep -E "[^[:digit:]]*6" /etc/centos-release
CentOS release 6.5 (Final)
[root@ambari-server-vm ~] # grep -E "[^[:digit:]]*5" /etc/centos-release
CentOS release 6.5 (Final)
{code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message