Bug 1388685

Summary: current 7.3 AH autobrew compose failure
Product: Red Hat Enterprise Linux 7 Reporter: Colin Walters <walters>
Component: dockerAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED CURRENTRELEASE QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: amurdaca, dwalsh, lsm5, miabbott, tdawson
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: docker-1.12.1-7.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-28 13:36:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Colin Walters 2016-10-25 21:53:59 UTC
Looking at:

https://atomic-e2e-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhelah-autobrew-7.3-treecompose/66/console

I am confused with the docker versioning in
http://pkgs.devel.redhat.com/cgit/rpms/docker/log/?h=extras-rhel-7.3

The version number seems to have gone backwards in
Brew specifically:
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=518021
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=520103

Which ordinarily may be OK except I think in this case one
of the repos picked up an older build with a higher version.

Comment 2 Lokesh Mandvekar 2016-10-26 02:29:39 UTC
I didn't think this would be an issue since the version that will be released next would be 1.10.3 and 1.12.1 is still ahead of it. Anyway, I can bump the Epoch if it's causing internal chaos.

Comment 3 Daniel Walsh 2016-10-26 11:38:05 UTC
Colin 7.3.0 is supposed to go out with 1.10.3  7.3.1 is going to go out with docker-1.12.*.  

The problem was that everything was frozen for 7.3.0 and we were working on 7.3.1, but then OpenShift found a problem which caused us to go up the docker-1.10 version for 7.3.0.

Comment 4 Colin Walters 2016-10-27 13:37:06 UTC
Ok, now we have a new issue in that when docker/docker-latest match, they conflict:

https://atomic-e2e-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhelah-autobrew-7.3-treecompose/108/console

09:13:50 error: Error running transaction: file /usr/libexec/docker/docker-containerd conflicts between attemped installs of docker-latest-1.12.2-1.el7.x86_64
09:13:50 file /usr/libexec/docker/docker-containerd-shim conflicts between attemped installs of docker-latest-1.12.2-1.el7.x86_64
09:13:50 file /usr/libexec/docker/docker-ctr conflicts between attemped installs of docker-latest-1.12.2-1.el7.x86_64
09:13:50 file /usr/libexec/docker/docker-runc conflicts between attemped installs of docker-latest-1.12.2-1.el7.x86_64

Comment 8 Troy Dawson 2016-11-22 15:23:30 UTC
(In reply to Lokesh Mandvekar from comment #2)
> I didn't think this would be an issue since the version that will be
> released next would be 1.10.3 and 1.12.1 is still ahead of it. Anyway, I can
> bump the Epoch if it's causing internal chaos.

The damage is already done.  I'm just letting you know that system administrators for years to come will look at this comment and say "This was the change.  This is the starting point that started all our pain."

It's too late now, but please, please, please do not use Epoch's so lightly.

Comment 9 Lokesh Mandvekar 2016-11-22 18:26:12 UTC
(In reply to Troy Dawson from comment #8)
> (In reply to Lokesh Mandvekar from comment #2)
> > I didn't think this would be an issue since the version that will be
> > released next would be 1.10.3 and 1.12.1 is still ahead of it. Anyway, I can
> > bump the Epoch if it's causing internal chaos.
> 
> The damage is already done.  I'm just letting you know that system
> administrators for years to come will look at this comment and say "This was
> the change.  This is the starting point that started all our pain."
> 
> It's too late now, but please, please, please do not use Epoch's so lightly.

Is there an option other than bumping Epoch when it comes to downgrading?