You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/05/04 20:15:00 UTC
[jira] [Commented] (AMBARI-23756) Ambari Infra Solr Service Check
fails after Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464344#comment-16464344 ]
Hudson commented on AMBARI-23756:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9184 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9184/])
[AMBARI-23756] Ambari Infra Solr Service Check fails after Ambari (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=b0e5419778b3dd95f1f81ca2da1b297e0ad12ef9])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClustersImpl.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog270.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Clusters.java
> Ambari Infra Solr Service Check fails after Ambari Upgrade
> ----------------------------------------------------------
>
> Key: AMBARI-23756
> URL: https://issues.apache.org/jira/browse/AMBARI-23756
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Jasmeen Kaur
> Assignee: Robert Levas
> Priority: Critical
> Labels: pull-request-available, upgrade
> Fix For: 2.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> *STR*
> 1) Upgrade Ambari from 2.6.X to 2.7.0.0-435 ( Unkerberized cluster)
> 2) Upgrade Non Stack Services, like Infra Solr.
> 3) Restart all required services (which might have stale configs)
> 4) Run Service check on Ambari Infra Solr . It fails with below error
> {code:java}
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/service_check.py", line 48, in <module>
> InfraServiceCheck().execute()
> File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 353, in execute
> method(env)
> File "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/service_check.py", line 27, in service_check
> import params
> File "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/params.py", line 109, in <module>
> infra_solr_java_stack_size = format(config['configurations']['infra-solr-env']['infra_solr_java_stack_size'])
> File "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/format.py", line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
> File "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/format.py", line 59, in format
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 558, in _vformat
> self.parse(format_string):
> File "/usr/lib64/python2.7/string.py", line 621, in parse
> return format_string._formatter_parser()
> File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py", line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'infra_solr_java_stack_size' was not found in configurations dictionary!
> {code}
> *Cause*
> While upgrading the name of the AMBARI_INFRA service is changed to AMBARI_INFRA_SOLR, but the old name is cached in the JPA entities cause a mismatch on services names at some point.
> *Solution*
> Clear the JPA entity cache after changing the AMBARI_INFRA service name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)