Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:


Version-Release number of selected component (if applicable):
Yum reports transcation error while performing yum update on 6.3.1 box 

How reproducible:
Always

Steps to Reproduce:
1. Set the 6.4.0 snap1 repo 
2. perform yum update
3.

Actual results:
Running transaction check
ERROR with transaction check vs depsolve:
/usr/bin/ruby193-ruby is needed by (installed) ruby193-rubygem-archive-tar-minitar-0.5.2-9.el7.noarch
 You could try running: rpm -Va --nofiles --nodigest
Your transaction was saved, rerun it with:
 yum load-transaction /tmp/yum_save_tx.2018-04-30.04-16.RtBZDI.yumtx


Expected results:
Yum update should be successsful

Additional info:

Build : Satellite 6.4.0 snap2

========== SATELLITE UPGRADE =================

Time taken for satellite packages update- 0:18:02
Time taken for Satellite Upgrade - 0:19:56
The Satellite is upgraded from 6.3.1 to 6.4.0

Workaround:

When doing the upgrade, use:

yum update satellite foreman-proxy-content

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927