<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Ambari 2.4.2 upgrade to Ambari 2.5.0 build 1087 in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-4-2-upgrade-to-Ambari-2-5-0-build-1087/m-p/141557#M56336</link>
    <description>&lt;P&gt;&lt;STRONG&gt;I'm doing the following&lt;/STRONG&gt;&lt;/P&gt;&lt;PRE&gt;sudo yum update ambari-server&lt;/PRE&gt;
&lt;PRE&gt;sudo ambari-server upgrade

Using python  /usr/bin/pythonUpgrading ambari-serverERROR: Unexpected TypeError:
print_info_msg() takes exactly 1 argument (2 given)For more info run
ambari-server with -v or --verbose option&lt;/PRE&gt;
&lt;PRE&gt;sudo ambari-server upgrade -v

Using python  /usr/bin/pythonUpgrading ambari-serverINFO: Loading properties from
/etc/ambari-server/conf/ambari.propertiesTraceback (most recent call
last):  File "/usr/sbin/ambari-server.py",
line 941, in &amp;lt;module&amp;gt;  mainBody()  File "/usr/sbin/ambari-server.py",
line 911, in mainBody  main(options, args, parser)  File "/usr/sbin/ambari-server.py",
line 863, in main  action_obj.execute()  File "/usr/sbin/ambari-server.py",
line 78, in execute  self.fn(*self.args, **self.kwargs)  File
"/usr/lib/python2.6/site-packages/ambari_server/serverUpgrade.py",
line 337, in upgrade  print_info_msg("Upgrade Ambari
Server", True)TypeError: print_info_msg()
takes exactly 1 argument (2 given)&lt;/PRE&gt;&lt;P&gt;This is an HA NN and RM cluster with MIT
Kerberos on Centos 7.&lt;/P&gt;</description>
    <pubDate>Tue, 07 Mar 2017 05:08:54 GMT</pubDate>
    <dc:creator>aervits</dc:creator>
    <dc:date>2017-03-07T05:08:54Z</dc:date>
    <item>
      <title>Ambari 2.4.2 upgrade to Ambari 2.5.0 build 1087</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-4-2-upgrade-to-Ambari-2-5-0-build-1087/m-p/141557#M56336</link>
      <description>&lt;P&gt;&lt;STRONG&gt;I'm doing the following&lt;/STRONG&gt;&lt;/P&gt;&lt;PRE&gt;sudo yum update ambari-server&lt;/PRE&gt;
&lt;PRE&gt;sudo ambari-server upgrade

Using python  /usr/bin/pythonUpgrading ambari-serverERROR: Unexpected TypeError:
print_info_msg() takes exactly 1 argument (2 given)For more info run
ambari-server with -v or --verbose option&lt;/PRE&gt;
&lt;PRE&gt;sudo ambari-server upgrade -v

Using python  /usr/bin/pythonUpgrading ambari-serverINFO: Loading properties from
/etc/ambari-server/conf/ambari.propertiesTraceback (most recent call
last):  File "/usr/sbin/ambari-server.py",
line 941, in &amp;lt;module&amp;gt;  mainBody()  File "/usr/sbin/ambari-server.py",
line 911, in mainBody  main(options, args, parser)  File "/usr/sbin/ambari-server.py",
line 863, in main  action_obj.execute()  File "/usr/sbin/ambari-server.py",
line 78, in execute  self.fn(*self.args, **self.kwargs)  File
"/usr/lib/python2.6/site-packages/ambari_server/serverUpgrade.py",
line 337, in upgrade  print_info_msg("Upgrade Ambari
Server", True)TypeError: print_info_msg()
takes exactly 1 argument (2 given)&lt;/PRE&gt;&lt;P&gt;This is an HA NN and RM cluster with MIT
Kerberos on Centos 7.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2017 05:08:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-4-2-upgrade-to-Ambari-2-5-0-build-1087/m-p/141557#M56336</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2017-03-07T05:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari 2.4.2 upgrade to Ambari 2.5.0 build 1087</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-4-2-upgrade-to-Ambari-2-5-0-build-1087/m-p/141558#M56337</link>
      <description>&lt;P&gt;I was able to upgrade ambari-server, turns out ambari_commons.logging_utils.py changed print_msg_info() signature from one argument to two and I had ambari-agent still on the old version, the fix is upgrade ambari-server and agent at the same time if both coexist on a server, that way ambari_commons gets updated logging_utils package. In my case, I actually had to reinstall ambari and restore from backup as I messed up the whole thing trying out different scenarios. &lt;/P&gt;&lt;P&gt;this is new function signature &lt;A href="https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/ambari_commons/logging_utils.py" target="_blank"&gt;https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/ambari_commons/logging_utils.py&lt;/A&gt;&lt;/P&gt;&lt;PRE&gt;#
# Prints an "info" messsage.
#
def print_info_msg(msg, forced=False):
  if forced:
    print("INFO: " + msg)
    return
  if _VERBOSE:
    print("INFO: " + msg)
&lt;/PRE&gt;&lt;P&gt;this is an old one, from 2.4 branch &lt;A href="https://github.com/apache/ambari/blob/branch-2.4.0/ambari-common/src/main/python/ambari_commons/logging_utils.py" target="_blank"&gt;https://github.com/apache/ambari/blob/branch-2.4.0/ambari-common/src/main/python/ambari_commons/logging_utils.py&lt;/A&gt;&lt;/P&gt;&lt;PRE&gt;#
# Prints an "info" messsage.
#
def print_info_msg(msg):
  if _VERBOSE:
    print("INFO: " + msg)
&lt;/PRE&gt;</description>
      <pubDate>Thu, 09 Mar 2017 00:20:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-4-2-upgrade-to-Ambari-2-5-0-build-1087/m-p/141558#M56337</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2017-03-09T00:20:23Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari 2.4.2 upgrade to Ambari 2.5.0 build 1087</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-4-2-upgrade-to-Ambari-2-5-0-build-1087/m-p/141559#M56338</link>
      <description>&lt;P&gt;addendum: the order of install and upgrade of ambari-server matters and it is the same for Ambari 2.4.2 as well. Morale of the story, read the documentation fully &lt;A href="http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-upgrade/content/upgrade_ambari.html" target="_blank"&gt;http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-upgrade/content/upgrade_ambari.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2017 00:33:17 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-4-2-upgrade-to-Ambari-2-5-0-build-1087/m-p/141559#M56338</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2017-03-09T00:33:17Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari 2.4.2 upgrade to Ambari 2.5.0 build 1087</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-4-2-upgrade-to-Ambari-2-5-0-build-1087/m-p/141560#M56339</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/393/aervits.html" nodeid="393"&gt;@Artem Ervits&lt;/A&gt; &lt;/P&gt;&lt;P&gt;According to the upgrade instructions from 2.4.2 &lt;A href="http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-upgrade/content/upgrade_ambari.html" target="_blank"&gt;http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-upgrade/content/upgrade_ambari.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You upgrade server, then agent and then upgrade the DB schema - 'ambari-server upgrade'&lt;/P&gt;&lt;P&gt;The order is important and should be the same for 2.5.0 as well&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2017 00:33:42 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-4-2-upgrade-to-Ambari-2-5-0-build-1087/m-p/141560#M56339</guid>
      <dc:creator>vsharma</dc:creator>
      <dc:date>2017-03-09T00:33:42Z</dc:date>
    </item>
  </channel>
</rss>

