ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-16881) ZKFC restart failed during EU with 'upgrade_type' not defined error
Date Wed, 25 May 2016 16:41:12 GMT
Vitaly Brodetskyi created AMBARI-16881:
------------------------------------------

             Summary: ZKFC restart failed during EU with 'upgrade_type' not defined error
                 Key: AMBARI-16881
                 URL: https://issues.apache.org/jira/browse/AMBARI-16881
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.4.0
            Reporter: Vitaly Brodetskyi
            Assignee: Vitaly Brodetskyi
            Priority: Blocker
             Fix For: 2.4.0


Steps
Deploy HDP-2.4.2 cluster with Ambari 2.2.2 (Secure, HA cluster)
Upgrade Ambari to 2.4.0.0
Perform EU to 2.5.0.0-555
Result
ZKFC restart failed with below error:
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py",
line 200, in <module>
    ZkfcSlave().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 257, in execute
    method(env)
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 668, in restart
    self.status(env)
  File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py",
line 102, in status
    ZkfcSlaveDefault.status_static(env, upgrade_type)
NameError: global name 'upgrade_type' is not defined



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

Mime
View raw message