ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonenko Alexander (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-10296) UI hard codes OS family mappings causing hostChecks to fail
Date Tue, 31 Mar 2015 17:01:52 GMT
Antonenko Alexander created AMBARI-10296:
--------------------------------------------

             Summary: UI hard codes OS family mappings causing hostChecks to fail
                 Key: AMBARI-10296
                 URL: https://issues.apache.org/jira/browse/AMBARI-10296
             Project: Ambari
          Issue Type: Task
          Components: ambari-web
    Affects Versions: 2.1.0
            Reporter: Antonenko Alexander
            Assignee: Antonenko Alexander
             Fix For: 2.1.0


UI should use "/api/v1/hosts/host_name?fields=Hosts/os_family" to check repository OS (when
it will be added to the api)

Problem:
We have one place to store os_types and related os_families - os_family.json
After adding a new OS to os_family.json host check fails.
{noformat:title=Host Check/Repository Issues}
Host (centos703) is centos7 OS type, but the repositories chosen in "Select Stack" 
step was redhat5,redhat6,redhat7,suse11,ubuntu12. Selected repositories do not 
support this host OS type.
{noformat}
Code to determine OS type from the OS family is located here:
app/controllers/wizard/step3_controller.js:1268 (repoToAgentOsType)
It duplicates os_family.json logic. 
We can add OS_Family to {{/api/v1/hosts/host_name}} (like "os_type" : "centos7" we can add
"os_family" : "redhat7") and get rid of UI os_family determination code.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message