You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2017/08/29 14:48:00 UTC

[jira] [Updated] (AMBARI-21843) Database consistency check fails after upgrade to ambari 2.6.0

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

Vitaly Brodetskyi updated AMBARI-21843:
---------------------------------------
    Attachment: AMBARI-21843.patch

> Database consistency check fails after upgrade to ambari 2.6.0
> --------------------------------------------------------------
>
>                 Key: AMBARI-21843
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21843
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.6.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21843.patch
>
>
> Here we need to fix two issues:
> 1) Table "clusterconfigmapping" was removed in ambari-2.6.0 (dropping it during upgrade). But db consistency check still using this table to get some data. After upgrade it fails because "clusterconfigmapping" doesn't exist. Need to reimplement checks which are using this table.
> 2) Db consistency check doesn't show any information for user about errors, in casse when table doesn't exist. You can check that with "clusterconfigmapping"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)