<?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 Re: how to resolve - Incomplete Yum Transactions when performing HDP upgrade in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-resolve-Incomplete-Yum-Transactions-when-performing/m-p/231831#M75012</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Please try this:&lt;BR /&gt;&lt;BR /&gt;1. Cleanup/Remove some old files at &lt;STRONG&gt;"/var/lib/yum/transaction*" &lt;/STRONG&gt;which are old transactions and not cleaned up by any chance.&lt;BR /&gt;&lt;BR /&gt;2. Use the "yum-complete-transaction" utility to cleanup old incomplete transactions:&lt;/P&gt;&lt;PRE&gt;# yum install yum-utils -y

# yum-complete-transaction --cleanup-only
(OR)
# yum-complete-transaction&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Then retry the installation process.  Please run these commands on all those hosts where the installation failed.&lt;/P&gt;</description>
    <pubDate>Mon, 26 Feb 2018 20:41:14 GMT</pubDate>
    <dc:creator>jsensharma</dc:creator>
    <dc:date>2018-02-26T20:41:14Z</dc:date>
    <item>
      <title>how to resolve - Incomplete Yum Transactions when performing HDP upgrade</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-resolve-Incomplete-Yum-Transactions-when-performing/m-p/231830#M75011</link>
      <description>&lt;P&gt;we are in the middle of HDP upgrade to 2.6.4&lt;/P&gt;&lt;P&gt;but on all cluster nodes we get the following errors during installation &lt;/P&gt;&lt;P&gt;how to resolve this isshue ?&lt;/P&gt;&lt;PRE&gt;2018-02-26 12:27:37,484 - *** Incomplete Yum Transactions ***
2018-02-26 12:27:37,484 -     
2018-02-26 12:27:37,484 - Ambari has detected that there are incomplete Yum transactions on this host. This will interfere with the installation process and must be resolved before continuing.
2018-02-26 12:27:37,485 - 
2018-02-26 12:27:37,485 - - Identify the pending transactions with the command 'yum history list &amp;lt;packages failed&amp;gt;'
2018-02-26 12:27:37,485 - - Revert each pending transaction with the command 'yum history undo'
2018-02-26 12:27:37,485 - - Flush the transaction log with 'yum-complete-transaction --cleanup-only'
2018-02-26 12:27:37,485 - 
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py", line 473, in &amp;lt;module&amp;gt;
    InstallPackages().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 375, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py", line 133, in actionexecute
    raise Fail("Failed to distribute repositories/install packages")
resource_management.core.exceptions.Fail: Failed to distribute repositories/install packages&lt;/PRE&gt;</description>
      <pubDate>Mon, 26 Feb 2018 20:32:07 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-resolve-Incomplete-Yum-Transactions-when-performing/m-p/231830#M75011</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2018-02-26T20:32:07Z</dc:date>
    </item>
    <item>
      <title>Re: how to resolve - Incomplete Yum Transactions when performing HDP upgrade</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-resolve-Incomplete-Yum-Transactions-when-performing/m-p/231831#M75012</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Please try this:&lt;BR /&gt;&lt;BR /&gt;1. Cleanup/Remove some old files at &lt;STRONG&gt;"/var/lib/yum/transaction*" &lt;/STRONG&gt;which are old transactions and not cleaned up by any chance.&lt;BR /&gt;&lt;BR /&gt;2. Use the "yum-complete-transaction" utility to cleanup old incomplete transactions:&lt;/P&gt;&lt;PRE&gt;# yum install yum-utils -y

# yum-complete-transaction --cleanup-only
(OR)
# yum-complete-transaction&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Then retry the installation process.  Please run these commands on all those hosts where the installation failed.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Feb 2018 20:41:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-resolve-Incomplete-Yum-Transactions-when-performing/m-p/231831#M75012</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2018-02-26T20:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: how to resolve - Incomplete Yum Transactions when performing HDP upgrade</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-resolve-Incomplete-Yum-Transactions-when-performing/m-p/231832#M75013</link>
      <description>&lt;P&gt;now we install again ( re-install ) , from ambari GUI ( upgrade ) &lt;/P&gt;&lt;P&gt;but we get now the following down&lt;/P&gt;&lt;P&gt;its very strange because we  set in the ambari GUI the repo for HDP , SDP-GPL and HDP-UTILS&lt;/P&gt;&lt;P&gt;and also the 3 repo also exists on each machine&lt;/P&gt;&lt;P&gt;what is unclear is that&lt;/P&gt;&lt;P&gt;when we try to install the pkg  on the machine&lt;/P&gt;&lt;PRE&gt;/usr/bin/yum -d 0 -e 0 -y install '--disablerepo=*' --enablerepo=HDP-2.6-GPL-repo-53,HDP-2.6-repo-53,HDP-UTILS-1.1.0.22-repo-53 hdp-select
Package hdp-select-2.6.4.0-91.noarch already installed and latest version&lt;/PRE&gt;&lt;P&gt;then its tell us that pkg already exists&lt;/P&gt;&lt;P&gt;but from the log seems that he not found the pkg -  hdp-select &lt;/P&gt;&lt;P&gt;how it can be?&lt;/P&gt;&lt;PRE&gt;&amp;lt;br&amp;gt;2018-02-26 13:59:25,315 - Will install packages for repository version 2.6.4.0
2018-02-26 13:59:25,316 - Repository['HDP-2.6-repo-53'] {'append_to_file': False, 'base_url': 'http://98.45.232.167/HDP/centos7/2.6.4.0-91', 'action': ['create'], 'components': [u'HDP', 'main'], 'repo_template': '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list %}mirrorlist={{mirror_list}}{% else %}baseurl={{base_url}}{% endif %}\n\npath=/\nenabled=1\ngpgcheck=0', 'repo_file_name': 'ambari-hdp-53', 'mirror_list': None}
2018-02-26 13:59:25,333 - File['/etc/yum.repos.d/ambari-hdp-53.repo'] {'content': '[HDP-2.6-repo-53]\nname=HDP-2.6-repo-53\nbaseurl=http://98.45.232.167/HDP/centos7/2.6.4.0-91\n\npath=/\nenabled=1\ngpgcheck=0'}
2018-02-26 13:59:25,334 - Writing File['/etc/yum.repos.d/ambari-hdp-53.repo'] because contents don't match
2018-02-26 13:59:25,335 - Repository['HDP-2.6-GPL-repo-53'] {'append_to_file': True, 'base_url': 'http://98.45.232.167/HDP-GPL/centos7/2.6.4.0-91', 'action': ['create'], 'components': [u'HDP-GPL', 'main'], 'repo_template': '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list %}mirrorlist={{mirror_list}}{% else %}baseurl={{base_url}}{% endif %}\n\npath=/\nenabled=1\ngpgcheck=0', 'repo_file_name': 'ambari-hdp-53', 'mirror_list': None}
2018-02-26 13:59:25,343 - File['/etc/yum.repos.d/ambari-hdp-53.repo'] {'content': '[HDP-2.6-repo-53]\nname=HDP-2.6-repo-53\nbaseurl=http://98.45.232.167/HDP/centos7/2.6.4.0-91\n\npath=/\nenabled=1\ngpgcheck=0\n[HDP-2.6-GPL-repo-53]\nname=HDP-2.6-GPL-repo-53\nbaseurl=http://98.45.232.167/HDP-GPL/centos7/2.6.4.0-91\n\npath=/\nenabled=1\ngpgcheck=0'}
2018-02-26 13:59:25,343 - Writing File['/etc/yum.repos.d/ambari-hdp-53.repo'] because contents don't match
2018-02-26 13:59:25,344 - Repository['HDP-UTILS-1.1.0.22-repo-53'] {'append_to_file': True, 'base_url': 'http://98.45.232.167/', 'action': ['create'], 'components': [u'HDP-UTILS', 'main'], 'repo_template': '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list %}mirrorlist={{mirror_list}}{% else %}baseurl={{base_url}}{% endif %}\n\npath=/\nenabled=1\ngpgcheck=0', 'repo_file_name': 'ambari-hdp-53', 'mirror_list': None}
2018-02-26 13:59:25,352 - File['/etc/yum.repos.d/ambari-hdp-53.repo'] {'content': '[HDP-2.6-repo-53]\nname=HDP-2.6-repo-53\nbaseurl=http://98.45.232.167/HDP/centos7/2.6.4.0-91\n\npath=/\nenabled=1\ngpgcheck=0\n[HDP-2.6-GPL-repo-53]\nname=HDP-2.6-GPL-repo-53\nbaseurl=http://98.45.232.167/HDP-GPL/centos7/2.6.4.0-91\n\npath=/\nenabled=1\ngpgcheck=0\n[HDP-UTILS-1.1.0.22-repo-53]\nname=HDP-UTILS-1.1.0.22-repo-53\nbaseurl=http://98.45.232.167/\n\npath=/\nenabled=1\ngpgcheck=0'}
2018-02-26 13:59:25,353 - Writing File['/etc/yum.repos.d/ambari-hdp-53.repo'] because contents don't match
2018-02-26 13:59:25,354 - Yum non-completed transactions check passed
2018-02-26 13:59:25,354 - call[('ambari-python-wrap', u'/usr/bin/hdp-select', 'versions')] {}
2018-02-26 13:59:25,426 - call returned (0, '2.6.0.3-8\n2.6.4.0-91')
2018-02-26 13:59:25,427 - Package['hdp-select'] {'retry_on_repo_unavailability': False, 'retry_count': 5, 'use_repos': {u'HDP-2.6-repo-53': u'ambari-hdp-53', u'HDP-2.6-GPL-repo-53': u'ambari-hdp-53', u'HDP-UTILS-1.1.0.22-repo-53': u'ambari-hdp-53'}, 'action': ['upgrade']}
2018-02-26 13:59:25,428 - Installing package hdp-select ('/usr/bin/yum -d 0 -e 0 -y install '--disablerepo=*' --enablerepo=HDP-2.6-GPL-repo-53,HDP-2.6-repo-53,HDP-UTILS-1.1.0.22-repo-53 hdp-select')
2018-02-26 13:59:27,565 - Looking for matching packages in the following repositories: HDP-2.6-repo-53, HDP-2.6-GPL-repo-53, HDP-UTILS-1.1.0.22-repo-53
2018-02-26 13:59:35,337 - No package found for hadoop_${stack_version}(hadoop_(\d|_)+$)&amp;lt;br&amp;gt;&lt;/PRE&gt;
&lt;PRE&gt;&amp;lt;br&amp;gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 26 Feb 2018 22:10:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-resolve-Incomplete-Yum-Transactions-when-performing/m-p/231832#M75013</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2018-02-26T22:10:10Z</dc:date>
    </item>
  </channel>
</rss>

