ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Tkach (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20449) Upgrade pre-checks screen does not show CONFIG_MERGE warning
Date Tue, 14 Mar 2017 19:23:41 GMT

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

Andrii Tkach updated AMBARI-20449:
----------------------------------
    Status: Patch Available  (was: Open)

> Upgrade pre-checks screen does not show CONFIG_MERGE warning
> ------------------------------------------------------------
>
>                 Key: AMBARI-20449
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20449
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Blocker
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20449_branch-2.5.patch, AMBARI-20449.patch, Screen Shot 2017-03-13
at 6.49.59 PM.png, Screen Shot 2017-03-13 at 6.50.03 PM.png
>
>
> *STR*
> # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1
> # Register HDP-2.6 version and install the bits
> # Click on Upgrade and click on Warning hyperlink for EU
> *Result*: 
> Shows 2 warnings for EU. Click on the Warning and it shows "only one warning" and the
warning for CONFIG_MERGE pre-check does not show up
> (see attachments)
> From the output of pre-checks API call, I do see two warning for Config Merge as below:
> {code}
>       "href" : "http://172.22.81.58:8080/api/v1/clusters/cl1/rolling_upgrades_check/CONFIG_MERGE",
>       "UpgradeChecks" : {
>         "check" : "Configuration Merge Check",
>         "check_type" : "CLUSTER",
>         "cluster_name" : "cl1",
>         "failed_detail" : [
>           {
>             "type" : "topology",
>             "property" : "content",
>             "current" : "<topology>\n\n            <gateway>\n\n        
       <provider>\n                    <role>authentication</role>\n   
                <name>ShiroProvider</name>\n                    <enabled>true</enabled>\n
                   <param>\n                        <name>sessionTimeout</name>\n
                       <value>30</value>\n                    </param>\n
                   <param>\n                        <name>main.ldapRealm</name>\n
                       <value>org.apache.hadoop.gateway.shirorealm.KnoxLdapRealm</value>\n
                   </param>\n                    <param>\n                   
    <name>main.ldapRealm.userDnTemplate</name>\n                        <value>uid=
>         "id" : "CONFIG_MERGE",
>         "reason" : "The following config types will have values overwritten: hive-interactive-env,
topology, hadoop-env",
>         "repository_version" : "2.6.0.2-24",
>         "status" : "WARNING",
>         "upgrade_type" : "NON_ROLLING"
>       }
>     }
>     "id" : "HEALTH",
>         "reason" : "The following issues have been detected on this cluster and should
be addressed before upgrading: CRITICAL: NameNode Last Checkpoint: nats11-46-tups-erm16tofnsecha-s11-5.openstacklocal\nCRITICAL:
NameNode Last Checkpoint: nats11-46-tups-erm16tofnsecha-s11-1",
>         "repository_version" : "2.6.0.2-24",
>         "status" : "WARNING",
>         "upgrade_type" : "NON_ROLLING"
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message