ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18766) Add Service failed when none of the host components report version
Date Thu, 10 Nov 2016 03:11:58 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652858#comment-15652858
] 

Hadoop QA commented on AMBARI-18766:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12838259/AMBARI-18766.2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-web.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/9209//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9209//console

This message is automatically generated.

> Add Service failed when none of the host components report version
> ------------------------------------------------------------------
>
>                 Key: AMBARI-18766
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18766
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Sumit Mohanty
>            Assignee: Jaimin Jetly
>            Priority: Critical
>             Fix For: 2.4.2
>
>         Attachments: AMBARI-18766.2.patch, AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report version
(basically distro-select is not supported) then the stack version associated with the cluster
is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the cluster. UI
instead should simply rely on the stack version that is specified in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1",
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1",
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}



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

Mime
View raw message