ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-14944) Refactor how reported versions are handled
Date Fri, 05 Feb 2016 15:23:39 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-14944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Lysnichenko updated AMBARI-14944:
----------------------------------------
    Component/s: ambari-server

> Refactor how reported versions are handled
> ------------------------------------------
>
>                 Key: AMBARI-14944
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14944
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>         Attachments: AMBARI-14944.patch
>
>
> Need to revisit how reported versions affect RU/SWU/PU.  With PU, the version returned
is not going to be the same as the other components in the cluster.  This means when a version
is reported, we must check that against the repo version that it's for, and save the actual_version
in the hostcomponent "standard" data.



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

Mime
View raw message