You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Myroslav Papirkovskyi (JIRA)" <ji...@apache.org> on 2018/06/15 17:21:00 UTC
[jira] [Resolved] (AMBARI-24112) Requests failed after Ambari
upgrade with exception while executing custom service command
[ https://issues.apache.org/jira/browse/AMBARI-24112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myroslav Papirkovskyi resolved AMBARI-24112.
--------------------------------------------
Resolution: Fixed
Merged to trunk
> Requests failed after Ambari upgrade with exception while executing custom service command
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-24112
> URL: https://issues.apache.org/jira/browse/AMBARI-24112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Myroslav Papirkovskyi
> Assignee: Myroslav Papirkovskyi
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> *STR*
> # Deployed cluster with Ambari version: 2.6.2
> # Upgrade Ambari to Target Version: 2.7.0
> # Restart all services with stale configs
> *Result*
> Some of the requests failed with below error
> {code:java}
> stderr:
> Caught an exception while executing custom service command: : 'Metadata for cluster_id=2 is missing. Check if server sent it.'; 'Metadata for cluster_id=2 is missing. Check if server sent it.'
> stdout:
> Caught an exception while executing custom service command: : 'Metadata for cluster_id=2 is missing. Check if server sent it.'; 'Metadata for cluster_id=2 is missing. Check if server sent it.'
> Command failed after 1 tries{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)