ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayush Luniya (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-16030) Ambari operation history: Add ambari_operation_history table for record keeping history of ambari versions and operations
Date Mon, 11 Jul 2016 17:50:14 GMT

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

Jayush Luniya updated AMBARI-16030:
-----------------------------------
    Fix Version/s:     (was: 2.4.0)
                   2.5.0

> Ambari operation history: Add ambari_operation_history table for record keeping history
of ambari versions and operations
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-16030
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16030
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Nahappan Somasundaram
>            Assignee: Nahappan Somasundaram
>             Fix For: 2.5.0
>
>
> When investigating upgrade issues, information about history about Ambari versions is
missing. Also information about when the Ambari upgrades actually happened in the past is
completely missing. 
> Instead of relying on this information to be provided, Ambari should record Ambari upgrade
history in Ambari DB. 
> {noformat}
> ambari_version_history
> Version                    Date                                    Notes
> 2.2.2.0-1            02/09/2015 01:00:00                Clean Install
> 2.2.3.0-2            03/10/2015 01:00:00                Upgraded 2.2.2.0-1 -> 2.2.3.0-2
> 2.4.0.0-3            06/09/2015 01:00:00                Upgraded 2.2.3.0-2 -> 2.4.0.0-3
> {noformat}



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

Mime
View raw message