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-17604) Ambari server start fails after upgrade due to missing atlas-application configs
Date Thu, 07 Jul 2016 11:26:10 GMT

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

Hadoop QA commented on AMBARI-17604:
------------------------------------

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

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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-server.

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

This message is automatically generated.

> Ambari server start fails after upgrade due to missing atlas-application configs
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-17604
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17604
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17604.patch
>
>
> Likely caused by fix AMBARI-17573
> **Steps**
>   1. Deploy HDP-2.3.4.0 with Ambari 2.2.0.0
>   2. Upgrade Ambari to 2.4.0.0
>   3. Run ambari-server start
> **Result**  
> Failed with below error:    
>     
>     
>     ambari-server start
>     Using python  /usr/bin/python
>     Starting ambari-server
>     Ambari Server running with administrator privileges.
>     Organizing resource files at /var/lib/ambari-server/resources...
>     Ambari database consistency check started...
>     DB configs consistency check failed. Run "ambari-server start --skip-database-check"
to skip. If you use this "--skip-database-check" option, do not make any changes to your cluster
topology or perform a cluster upgrade until you correct the database consistency issues. See
"/var/log/ambari-server/ambari-server-check-database.log" for more details on the consistency
issues.
>     Ambari database consistency check finished
>     
> Log entry:
>     
>     
>     
>     2016-07-07 06:33:04,252  INFO - ******************************* Check database started
*******************************
>     2016-07-07 06:33:08,700  INFO - Checking for configs not mapped to any cluster
>     2016-07-07 06:33:08,802  INFO - Checking for configs selected more than once
>     2016-07-07 06:33:08,808  INFO - Checking for hosts without state
>     2016-07-07 06:33:08,809  INFO - Checking host component states count equals host
component desired states count
>     2016-07-07 06:33:08,814  INFO - Checking services and their configs
>     2016-07-07 06:33:11,214 ERROR - Required config(s): falcon-atlas-application.properties
is(are) not available for service FALCON with service config version 5 in cluster cl1
>     2016-07-07 06:33:11,215 ERROR - Required config(s): hive-atlas-application.properties
is(are) not available for service HIVE with service config version 7 in cluster cl1
>     2016-07-07 06:33:11,674  INFO - ******************************* Check database completed
*******************************
>     
> ***Solution:***
> There is the same kind of situation with Ranger configs. In the case of Ranger configs
we just add them on upgrade even if the service they are for does not exist. 
> So implementing the same kind of solution here.



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

Mime
View raw message