[ https://issues.apache.org/jira/browse/AMBARI-22387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249987#comment-16249987 ]
Hudson commented on AMBARI-22387: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8383 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8383/]) AMBARI-22387. Create a Pre-Upgrade Check Warning About LZO. Fix import (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6e706d427f1f9bcfc61f986ea1a1d5f5a28d500f]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/LZOCheck.java > Create a Pre-Upgrade Check Warning About LZO > -------------------------------------------- > > Key: AMBARI-22387 > URL: https://issues.apache.org/jira/browse/AMBARI-22387 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.6.1 > Reporter: Dmitry Lysnichenko > Assignee: Dmitry Lysnichenko > Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22387.patch > > > Ambari has removed its native support of distributing and installing LZO when > the LZO codecs are enabled in {{core-site}}. For existing clusters where LZO > is enabled, this means that performing an upgrade will now require manual > user intervention to get the LZO packages installed. > A pre-upgrade check should be created which checks to see if LZO is enabled > in the cluster and then produces a {{WARNING}} to the user letting them know > that before upgrading, they'd need to distribute the appropriate LZO packages. -- This message was sent by Atlassian JIRA (v6.4.14#64029)