RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
yum upgrade
--> Finished Dependency Resolution
Error: docker conflicts with atomic-openshift-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Version-Release number of selected component (if applicable):
3.1.1.6

How reproducible:
Try running yum upgrade on a RHEL 7 box

Steps to Reproduce:
1. yum upgrade
2. see dependency break due to docker 1.9.1

Actual results:
Dependency failing

Expected results:
Clean Upgrade

Additional info:
Basically as it sits right now upgrading a host system is problematic as any automated process we have in place has the potential to break our OSE installation.

You should be able to 'yum install docker-1.8.2' preinstall to workaround this problem.  We're getting a build through testing as soon as we can to address this properly.

*** This bug has been marked as a duplicate of bug 1323057 ***

I think this bug is unique. Regardless of what we do in the installer or in atomic-openshift packaging a 'yum upgrade' after installing 3.1.1.6 will still fail without adding '--skip-broken' or upgrading to 3.2.

Reopening this.

As Scott mentioned in comment 2, right now I am unable to run yum upgrade on any of my OSE 3.1.* systems as they all fail due to the docker conflict. This has only been remedied by modifying our system upgrade procedure temporarily as to allow the rest of the system to upgrade on the necessary cycle.

Conflicts will be removed in an upcoming build.

@Lokesh,

An upcoming build of what? And is it out yet?

(In reply to Eric Jones from comment #6)
> @Lokesh,
> 
> An upcoming build of what? And is it out yet?

docker rpm, will be out in the next RHEL extras update.

The removal of conflicts between openshift and docker will be release noted.

CLOSED NEXTRELEASE as per QE.